🌱 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.

Summary by CodeRabbit

• Chores
  • Added automated workflow to identify and label inactive issues and pull requests after 60 days of inactivity, with exceptions for items labeled as security-related, critical, pinned, blocked, in-progress, under-review, enhancement, or tech-debt, and for all assigned items.

[coderabbitai]

Walkthrough

A GitHub Actions workflow is added to automatically manage stale issues and pull requests. The workflow runs daily at 01:00 UTC and marks issues/PRs as stale after 60 days of inactivity, with exemptions for specific labels and all assignees.

Changes

Cohort / File(s)

Summary

GitHub Actions Workflow \.github/workflows/stale\.yml

New workflow file added to automatically mark stale issues and PRs. Configured to run daily and manually dispatch. Uses actions/stale@v9 with 60-day inactivity threshold, custom stale messages, label application, and exemptions for security-related, critical, pinned, blocked, in-progress, under-review, enhancement, and tech-debt issues/PRs. Auto-close is disabled. Stale label is removed when issues/PRs are updated.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

• Single configuration file: No complex logic or control flow to validate
• Standard workflow syntax: Straightforward GitHub Actions YAML configuration
• May require attention on: Verification that the 60-day threshold aligns with project maintenance policy, and confirmation that exempt labels and auto-close behavior (disabled) match intended repository settings

Poem

🐰 A stale-cleaner hops into town,
Daily sweeping issues down,
Sixty days of silence, then a mark—
But keeping precious gems from dark,
With exemptions wise, the workflow grins! ✨

Pre-merge checks and finishing touches

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title "Add stale issue marking workflow" directly and clearly summarizes the main change in this pull request, which adds a new GitHub Actions workflow file (.github/workflows/stale.yml) configured to automatically mark stale issues and pull requests. The title is concise, specific, and accurately reflects the primary objective of the changeset. While it includes a decorative emoji, the text itself is descriptive and would allow a teammate scanning the repository history to immediately understand that this PR introduces stale issue automation.

✨ 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

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 42f3d69 and 6f2cf6c.

📒 Files selected for processing (1)

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

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: Build & test from commit
• GitHub Check: Build & test from commit

🔇 Additional comments (2)

.github/workflows/stale.yml (2)

1-48: Workflow configuration aligns well with PR objectives.

The workflow is correctly configured with appropriate triggers, permissions, and stale-marking logic. The 60-day inactivity threshold, disabled auto-close, exempt labels, and assignee exemptions all match the specified objectives.

---

43-44: Verify that exempt labels exist in the GitHub repository settings.

The workflow references eight exempt labels but no label configuration exists in the repository. The labels are only defined in stale.yml lines 43-44 and not documented elsewhere. Other templates use different labels (e.g., kind/bug, needs-triage in ISSUE_TEMPLATE/bug.yaml), indicating labels may not be centrally configured.

Manually verify these labels exist in your GitHub repository's label settings:

• security, critical, pinned, blocked, in-progress, under-review, enhancement, tech-debt

If they don't exist, the stale workflow exemptions will be ineffective.

---

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.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 28.68%. Comparing base (42f3d69) to head (6f2cf6c).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #589   +/-   ##
=======================================
  Coverage   28.68%   28.68%           
=======================================
  Files          32       32           
  Lines        3828     3828           
=======================================
  Hits         1098     1098           
  Misses       2592     2592           
  Partials      138      138           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.