ci: harden AI triage (idempotent, non-clobbering, tighter labels)#85
Merged
Conversation
…diff-only changes + type patch)
Contributor
There was a problem hiding this comment.
Pull request overview
This PR hardens the AI-driven issue triage workflow to be idempotent (edit/update a single triage comment) and non-clobbering on re-runs (avoid re-applying labels/fields once an issue has already been triaged), while tightening the model’s allowed label outputs.
Changes:
- Make the triage comment idempotent via a hidden
<!-- auto-triage -->marker and PATCH updates to the existing comment. - Skip label/field mutations on re-triage (marker present), refreshing only the comment content.
- Remove diff-derived change labels (
C: No Java,C: Structures) from the model schema + allowlist, and drop the non-functional issue-type PATCH.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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 #80, addressing four of the improvement items.
<!-- auto-triage -->marker; a re-run (reopen / manual dispatch) edits the existing comment instead of stacking a new one.C: No JavaandC: Structuresfrom the AI's allowedchanges(and the allowlist). Those are diff-derived (decided from a PR's changed files bylabeler.yml), not guessable from an issue - this is what caused the badC: No Javaon a Java fix in the backlog sweep.type=is an org-only feature and no-ops on this personal repo; removed the failing call. TheT:label conveys type.No-valid-JSON fallback now only re-adds
S: Untriagedon first triage (won't re-untriage an already-triaged issue on a transient model failure).