Repository navigation
Align issue and PR auto-close automation across Azure Monitor repositories #270
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.
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
Merged
Hector Hernandez (hectorhdzg)
merged 2 commits into
main
from
hectorh/align-issue-automation
Oct 22, 2026
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,53 @@ | ||
| # Shared stale/auto-close policy for Azure Monitor repositories. | ||
| # Keep this file identical across repos. Author follow-up for issues is handled separately by | ||
| # needs-author-feedback.yml / needs-author-feedback-followup.yml. | ||
| # | ||
| # A single actions/stale invocation is used on purpose: the action persists its progress under one | ||
| # fixed cache key, so multiple invocations in the same repo would overwrite each other's progress. | ||
| name: "Stale issue handler" | ||
| on: | ||
| workflow_dispatch: | ||
| schedule: | ||
| - cron: "0 7 * * *" | ||
|
|
||
| permissions: | ||
| actions: write | ||
| issues: write | ||
| pull-requests: write | ||
|
|
||
| concurrency: | ||
| group: stale-handler | ||
| cancel-in-progress: false | ||
|
|
||
| jobs: | ||
| # Issues: stale after 90 inactive days, closed 14 days later. | ||
| # PRs: stale after 30 inactive days, closed 14 days later. | ||
| # Oldest first and throttled so existing backlogs are worked down gradually; progress carries over between runs. | ||
| stale: | ||
| runs-on: ubuntu-latest | ||
| steps: | ||
| - uses: actions/stale@4391f3da665fdf50b6810c1a66712fb9ba21aa93 # v11.0.0 | ||
| with: | ||
| days-before-issue-stale: 90 | ||
| days-before-issue-close: 14 | ||
| days-before-pr-stale: 30 | ||
| days-before-pr-close: 14 | ||
| stale-issue-message: 'This issue has had no activity for 90 days and will be closed in 14 days. Comment or add the "keep" label to prevent closure.' | ||
| stale-pr-message: 'This PR has had no activity for 30 days and will be closed in 14 days. Comment, push changes, or add the "keep" label to prevent closure.' | ||
| close-issue-message: "Closing due to inactivity. Please comment if this is still relevant and we can reopen it." | ||
| close-pr-message: "Closing due to inactivity. Feel free to reopen when you are ready to continue." | ||
| stale-issue-label: "stale" | ||
| stale-pr-label: "stale" | ||
| close-issue-label: "closed" | ||
| close-pr-label: "closed" | ||
| close-issue-reason: "not_planned" | ||
| # PRs share the issue exemptions except `bug` (a bug label on a PR does not mean the PR should stay open) | ||
| # and `needs-author-feedback` (the feedback workflows handle issues only, so feedback-labeled PRs | ||
| # still need this inactivity policy to close). | ||
| exempt-issue-labels: "bug,keep,needs-author-feedback,needs-team-attention,waiting-external,waiting,waiting for backend fix,waiting - CDN deployment,fixed - waiting release" | ||
| exempt-pr-labels: "keep,needs-team-attention,waiting-external,waiting,waiting for backend fix,waiting - CDN deployment,fixed - waiting release" | ||
| exempt-all-milestones: true | ||
| exempt-all-assignees: false | ||
| exempt-draft-pr: false | ||
| ascending: true | ||
| operations-per-run: 25 |
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.