Re-vendor pr-draft-gate: this copy was two template revisions behind - #7
Merged
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
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.
This repo's vendored gate was stale, and it was stale because of me.
How it happened
This repo was the pilot for the estate-wide vendoring sweep on 2026-09-07 — the first repo the workflow was placed in, to prove the mechanism worked before running it against 130 others. It was vendored by hand from the template as it stood at that moment: 221 lines.
The template then moved twice while the sweep was still running —
tgwab-standards#149and#150took it to 229 and then 231 lines. The scripted sweep fetched the template fresh on every invocation, so all 130 subsequent repos received the current version. Only the hand-vendored pilot kept the old one.That is the ordinary shape of a pilot: the thing you did first, by hand, before the process existed to keep it current.
Why it went unnoticed for hours
scripts/gate-repos.txt— the input to the drift checker that compares deployed copies against the template — lists 12 repos. The estate has 130 active.So the checker guarding a 131-repo rollout can see 9% of it, and this repo is not among the twelve. The stale copy was invisible to the only control that exists to find stale copies.
A follow-up PR expands that list to the full estate. This one lands first deliberately: expanding the checker's coverage while a known-stale copy is still out there would turn it red on a defect already identified, which teaches people to ignore a new control on its first run.
What changed in the two revisions
Nothing behavioural for this repo — the job name is still
pr-draft-gate, which is what a ruleset's required status check matches, and the decision logic is unchanged. The additions are documentation and the pointer tocheck-draft-gate.test.shadded by#149.The file is now byte-identical to
origin/main's template, verified by sha rather than by line count.🤖 Generated with Claude Code
https://claude.ai/code/session_016beCydw4C9VrgL9eHzGUG2
Fleet: unattributed