🌱 Add stale issue marking workflow

[tsanders-rh]

This PR adds an automated workflow to mark stale issues and pull requests.

Configuration:

• Marks items as stale after 60 days of inactivity
• Does not auto-close items (only marks them)
• Exempts items with labels: security, critical, pinned, blocked, in-progress, under-review, enhancement, tech-debt
• Exempts items with assignees
• Automatically removes stale label when items are updated

The workflow runs daily at 1:00 AM UTC and can also be triggered manually.

[coderabbitai]

Warning

Rate limit exceeded

@tsanders-rh has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 12 minutes and 32 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 0d792e7 and c696099.

📒 Files selected for processing (1)

• .github/workflows/stale.yml (1 hunks)

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch add-stale-workflow

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}