Skip to content

Add stale issue cleanup workflow #3679

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
alltheseas wants to merge 2 commits into
base: master
Choose a base branch
from
+32 −0
Draft

Add stale issue cleanup workflow #3679

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5822489
Add stale issue cleanup workflow
alltheseas Mar 13, 2026
b6d6dcd
Bump actions/stale to v10 and relax stale threshold to 180 days
alltheseas Mar 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 32 additions & 0 deletions .github/workflows/stale.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,32 @@
name: Stale issue cleanup

on:
schedule:
- cron: '0 9 * * 1' # every Monday at 9am UTC

permissions:
issues: write

jobs:
stale:
runs-on: ubuntu-latest
steps:
- uses: actions/stale@v10
with:
days-before-stale: 180
days-before-close: 30
stale-issue-label: 'stalled'
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot Mar 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion | 🟠 Major

Document the required "stalled" label setup.

The workflow requires a "stalled" label to exist. The PR description mentions creating it with color #FFA500, but this should be documented in the repository (e.g., README.md or CONTRIBUTING.md) so maintainers understand the prerequisite.

As per coding guidelines: "Update documentation when workflows change, especially this file, README.md, or developer notes."

🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In @.github/workflows/stale.yml at line 18, Add documentation that the workflow
in .github/workflows/stale.yml depends on a repository label named "stalled"
(configured via the stale-issue-label key) and specify the required color
`#FFA500`; update README.md or CONTRIBUTING.md with a short section describing the
exact label name ("stalled"), color (`#FFA500`), and a one-line instruction for
maintainers on how to create the label via GitHub UI or gh CLI so the workflow
can run correctly.

stale-issue-message: >
This issue has had no activity for 180 days. This usually means
it's too big and should be broken down, is blocked and needs
attention, or isn't a priority right now.

It will be auto-closed in 30 days if there's no further activity.
Feel free to comment to keep it open, or close it if it's no longer relevant.
close-issue-message: >
Closed due to inactivity. Reopen anytime if this becomes relevant again.
exempt-issue-labels: 'bounty,security,regression,pinned'
exempt-all-assignees: true
days-before-pr-stale: -1
days-before-pr-close: -1
operations-per-run: 30