Consume py-canon's auto-merge instead of copying it - #18
Merged
Conversation
The arming fix in gojiplus/py-canon#21 reaches only repositories that consume the reusable workflow. Eight held copies, so it would have reached one. Verified against py-canon's reusable before switching: it is a superset of this copy, same coverage of the label, the sweep, the stale warning, the missing-required-context naming and GH_REPO. Nothing is lost by delegating. Co-Authored-By: Claude Opus 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.
Replaces a copied
dependabot-auto-merge.ymlwith the four-line shim preen already uses, delegating to py-canon'sreusable-dependabot-auto-merge.yml@v1.Why now: the auto-merge arming bug (gojiplus/py-canon#21) can only reach repos that consume the reusable workflow. Eight repos held copies, so a fix in py-canon would have reached exactly one of them — preen. Copying the fix into eight files is what the shim design exists to avoid; preen's own header says so: "All the logic lives in py-canon, so a fix there reaches this repo on its next run instead of waiting for someone to copy a file across."
Verified no regression before migrating. py-canon's reusable is a superset — 317 lines against this copy's 273 — with identical coverage of
ELIGIBLE_LABEL,STALE_AFTER_HOURS,never_reported, the sweep,gh label createandGH_REPO(the label fix landed today). Checked feature by feature rather than assumed.Sequencing:
@v1currently tracks py-canon's main, so this repo picks up the arming guard once py-canon#21 merges and v1 moves. Merging this PR before that is safe — it just means current behaviour, delivered from one place instead of nine.actionlint clean.
🤖 Generated with Claude Code