ci(github): enable stale issue closing - #15036
Merged
Merged
Conversation
Dry run (actions run 33772184852) confirmed exemptions and counts, so remove debug-only to go live. Findings from the dry run folded in: - operations-per-run raised to 2500: each marked issue costs ~3 API ops and the org rate limit is 15000/hr, so one run covers the backlog. - Issues assigned to active maintainers (DonLakeFlyer, HTRamsey) are exempt; assignments to inactive maintainers are allowed to age out. The pre-existing manually applied `stale` labels were removed from all 68 open issues beforehand so they get the normal 90+30 day cycle.
github-actions
Bot
added
github_actions
Contributor
|
See the Build Results workflow run for details. |
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
The configuration matches the documented rollout and supported actions/stale inputs.
Pull request overview
Enables live stale-issue management following the successful dry run.
Changes:
- Removes dry-run mode.
- Exempts active maintainers’ assigned issues.
- Raises the per-run operation limit to process the backlog.
File summaries
| File | Description |
|---|---|
.github/workflows/stale.yml |
Activates labeling/closing and updates exemptions and capacity. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 0
- Review effort level: Balanced
💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #15027. Removes
debug-onlyso the stale workflow starts labeling and closing.Dry-run results (run 33772184852)
Exemptions behaved as intended; no errors.
Changes from the dry-run config
operations-per-run: 2500(was 1500). The dry run showed each marked issue costs ~3 API ops and the org rate limit is 15000/hr, so a higher cap lets one run cover the full backlog with plenty of headroom.exempt-issue-assignees: 'DonLakeFlyer,HTRamsey'in both jobs. Issues assigned to active maintainers stay open; the ~35 assigned to maintainers no longer active on QGC are allowed to age out normally.Pre-work already done
The 68 open issues that carried a manually applied
stalelabel had that label removed so they enter the normal 90-day + 30-day cycle rather than closing on the first live run.What happens after merge
stalesilently (the dry-run counts above minus ~200 now exempt by assignee) (no comment).