feat: add manual-qa-required/qa-verified labels to AI-filed issues - #97
Merged
Merged
Conversation
Team asked for a way to flag which AI-filed issues need a manual look before acting, separate from the existing bug/feature type labels. Agent now decides manual-qa-required (confidence <70/100 or not directly reproduced) vs qa-verified per item, matching the confidence score and reproduction method it already writes in the issue body. Creates both labels on first use so a newly onboarded repo doesn't need them pre-created. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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
1 participant
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.
Summary
bug-report/feature-request, both already applied).manual-qa-required(confidence <70/100 or not directly reproduced) vsqa-verifiedper item, matched to the same confidence score and reproduction method it already writes in the issue body -- they must agree.gh label create ... || true) so a newly onboarded repo doesn't need them pre-created, same gap that already existed for the other AI-triage labels.Test plan
gh api .../contents?ref=<branch>that the pushed branch contains the change🤖 Generated with Claude Code