Skip to content

fix: enable stale cleanup after 74 inactive days - #575

Open
Suneha Bose (bosesuneha) wants to merge 1 commit into
Azure:mainfrom
bosesuneha:fix/stale-auto-close
Open

Suneha Bose (bosesuneha) wants to merge 1 commit into
Azure:mainfrom
bosesuneha:fix/stale-auto-close

Conversation

@bosesuneha

Copy link
Copy Markdown
Member

Summary

  • Grant the stale job issues: write and pull-requests: write so labels and comments are no longer blocked by token permissions.
  • Mark issues and PRs idle after 60 inactive days, then close after 14 more inactive days. New activity clears idle and restarts the cycle.
  • Use one stale-action step for both issues and PRs, preserving the backlog issue exemption and three-hour schedule.
  • Add warning and closure messages explaining the policy.

Matches the 60 + 14 day timing in Azure/draft#801, but covers both issues and PRs.

Validation

  • Configuration assertions for permissions, timing, messages, exemptions, activity reset, and schedule.
  • actionlint, Prettier, and git diff --check passed.
  • No live cleanup was triggered.

Rollout

Previously unlabeled items receive a warning and a 14-day grace period. Existing idle labels retain their history, so already-idle items may close on the first scheduled run.

Related: #572 also grants stale-job write permissions; this PR additionally enables cleanup and consolidates the two stale steps.

@bosesuneha
Suneha Bose (bosesuneha) requested a review from a team as a code owner October 22, 2026 07:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant