Improve oncall triage recency and engagement criteria#29460
Open
vishnukannaujia wants to merge 1 commit intoanthropics:mainfrom
Open
Improve oncall triage recency and engagement criteria#29460vishnukannaujia wants to merge 1 commit intoanthropics:mainfrom
vishnukannaujia wants to merge 1 commit intoanthropics:mainfrom
Conversation
This was referenced Feb 28, 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.
Why
Oncall triage can miss relevant high-engagement issues because the current CI command assumes
gh issue listis ordered by most recently updated issues.This behavior is called out in #21953.
What changed
Updated
.claude/commands/oncall-triage-ci.mdto make candidate discovery deterministic:search issueswith explicit sort and date filter:is:issue is:open sort:updated-desc updated:>=YYYY-MM-DDissue listordering for recency.Impact
Related