Consume py-canon's Dependabot auto-merge instead of copying it - #26
Merged
Conversation
This repo held a local copy of the auto-merge workflow with no `schedule` block. The scheduled half is the one that matters: GitHub silently disarms auto-merge -- measured on appeler/pranaam#29, disarmed four seconds after a docs workflow finished with a skipped job -- and `on: pull_request` never fires again, so the PR sits green and unmerged while every run reports success. Measured across the fleet: 57 open Dependabot PRs, 37 of them green and simply never merged, and only 1 carrying the eligibility label the sweep reads. Twenty-one repos had no sweep at all. The reusable version was published in gojiplus/py-canon#19, but it was distributed through the copier template -- and template changes reach existing repos never, so this repo never got it. Referencing it means the next fix arrives on the next run rather than waiting for someone to copy a file across.
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.
This repo held a local copy of the auto-merge workflow with no
scheduleblock. The scheduled half is the one that matters: GitHub silently disarms auto-merge — measured onappeler/pranaam#29, disarmed four seconds after a docs workflow finished with a skipped job — andon: pull_requestnever fires again, so the PR sits green and unmerged while every run reports success.Measured across the fleet before fixing this:
CLEAN— green and simply never merged21 repos had no sweep at all.
The reusable version was published in gojiplus/py-canon#19, but distributed through the copier template — and template changes reach existing repos never (gojiplus/py-canon#31). So this repo never got it.
This arrives as a PR rather than a direct push because this repo's ruleset requires status checks on
main; the other 24 took the push.