Vendor pr-draft-gate — DS §4 three-hand gate - #16
Merged
Conversation
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.
Vendors
templates/pr-draft-gate.yml, byte for byte, no substitution.Why:
tgwab-standards#144merged, sotemplates/ruleset-main.jsonnow requirespr-draft-gatebesideci, withbypass_actors: []. Applying that ruleset to a repo without this workflow requires a check that never reports — blocking every PR in the repo permanently, including the one that would fix it.Order matters. The
gate-skippedlabel was created estate-wide first:gh pr edit --add-labelfails on a label that does not exist, so a repo with the workflow and no label has a documented escape hatch that is inert.This PR changes no ruleset. Before anything requires
pr-draft-gatehere, confirm it actually reports on a PR in THIS repo — a workflow that fails to trigger is indistinguishable from an absent one until a ruleset makes that permanent.Also before applying a ruleset here: any PR whose head predates this workflow will never get the check and becomes unmergeable. Re-trigger those first (empty commit, or close-and-reopen).
Part of the estate-wide vendoring sweep, 2026-09-07.
🤖 Generated with Claude Code
https://claude.ai/code/session_016beCydw4C9VrgL9eHzGUG2