Repository navigation
fix(engineering): keep draft PRs out of review attention - #18
Merged
Merged
Conversation
- Exclude drafts from review and authored-PR action queues. - Surface personal draft mentions only as possible responses, never implicit review permission. - Preserve non-draft review decisions and selected-repository/read-only boundaries. - Cover draft requests, review history, mention locations, and partial collection with deterministic regressions.
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.
Summary
Draft PRs no longer enter GitHub attention's review or authored-PR action queues, even when a review is requested, a previous review was dismissed, or new commits arrive. A personal
@handlemention can still surface as an informational candidate for a possible response; reviewing that draft requires an explicit user request. Team review requests, team mentions and replies alone do not qualify.Non-draft review/re-request rules, explicit repository selection and read-only GitHub collection stay unchanged. Mention discovery retains its notification-window and access limitations; this is not a complete historical mention index.
Verification
bun run validate— validated all five plugins, both native catalogues and local Markdown references.bun test— 62 passed, 0 failed; 339 assertions. Draft regressions cover direct/team requests, re-requests, dismissed reviews, changed heads, personal mention locations, notification-only signals and partial collection.mainfixture report: a draft review request stays hidden, a personally mentioned draft appears as response-only information, and a ready review request needs action.allagentsdev/agent-plugins --days 1— exit 0, two open PRs, no notification threads, no coverage warnings. Draft combinations were exercised by fixtures, not claimed from this live sample.Post-Deploy Monitoring & Validation
No additional operational monitoring required: this is an on-demand, read-only helper with no service or GitHub mutation changes. After updating the installed skill, its next selected-repository report should keep drafts out of review work and label personal draft mentions as response-only candidates.