Repository navigation
Align issue and PR auto-close automation across Azure Monitor repositories - #1544
Merged
Hector Hernandez (hectorhdzg) merged 7 commits intoOct 22, 2026
Merged
Conversation
…ories - needs-author-feedback.yml / needs-author-feedback-followup.yml: notify the author when the label is added, remind at 7 days, close at 14 days, and drop the label when the author replies - stale.yml: 90 days stale + 14 days close for general inactivity (oldest first, throttled); PRs inactive 30 days marked abandoned; wontfix/abandoned closed after 14+14 days; jobs run sequentially Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Hector Hernandez (hectorhdzg)
changed the title
Hector Hernandez (hectorhdzg)
force-pushed
the
hectorh/align-issue-automation
branch
from
October 21, 2026 22:41
37f4668 to
1022286
Compare
- stale.yml: use a single actions/stale invocation. The action persists progress under one fixed cache key, so multiple throttled jobs overwrote each other's checkpoints. Issues: 90 days stale + 14 close. PRs: 30 days stale + 14 close. This replaces the separate abandoned/wontfix jobs, applies one consistent PR exemption list, and lets PRs labeled needs-author-feedback close normally. - needs-author-feedback-followup.yml: skip issues labeled keep, and remove the label before closing so an author reply racing the run (label already gone) leaves the issue open. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
- Re-check issue state, labels and author replies right before auto-closing - Remove needs-author-feedback only after a successful close so failures retry - Ignore applied markers from an earlier feedback round - Reopen auto-closed issues when the author replies - Exempt waiting labels for PRs too Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
- Skip auto-close if the label was reapplied during the run - Reopen if the author replied while the issue was being closed - Reply handler uses current issue state, ignores replies older than the latest label, and only reopens bot closures from the current round Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
- Read state_reason from the fetched issue (closed events do not expose it) - Count author replies from the latest label application so answers before a backfilled marker are honored Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Performance comparisonThreshold for gating regression: -15% (median ops/s)
✅ No gating regression beyond threshold.baseline: 2026-10-21T23:55:26.022Z (node v22.23.3, 3 samples × 5s) |
Jackson Weber (JacksonWeber)
approved these changes
Oct 22, 2026
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.
Aligns issue and PR auto-close automation across the Azure Monitor repositories so they all follow the same rules. The same three workflow files are used in each repo.
Rules
needs-author-feedbackneeds-author-feedbacklabel added / author commentsneeds-author-feedback-followupkeepopts out)stalestale, closed 14 days later. PRs: 30 days →stale, closed 14 days later. Oldest first and throttled so existing backlogs are worked down graduallystaleintentionally uses a singleactions/staleinvocation: the action persists its progress under one fixed cache key, so multiple invocations would overwrite each other's progress.Exempt from inactivity closure:
keep,needs-team-attention, waiting labels (waiting,waiting-external,waiting for backend fix,waiting - CDN deployment,fixed - waiting release), and milestoned items. Issues are also exempt when labeledbugorneeds-author-feedback(the latter is handled by the follow-up workflow). Any comment or update resets the clock.Feedback flow safeguards: the follow-up re-checks state, label round and author replies right before closing, removes the label only after a successful close (failures retry next run), and reopens if a reply races the close. The reply handler ignores replies older than the latest label, skips bot-authored issues, and never reverses a maintainer's manual close.
Follow-up (not in this PR)
Rename
need-author-feedbacktoneeds-author-feedbackso existing items are picked up.Repo-specific
stale.yml;enhancement/documentation/ assigned items are no longer exempt.