Auto-merge every green Dependabot update, majors included - #13
Merged
Conversation
The semver gate bought latency, not safety: every held-back major was merged unchanged once a person confirmed what the checks already said. The checks are the gate now; the no-automerge label is the manual hold. fetch-metadata is no longer needed, and the wait loop counts the rollup by bucket, so a cancelled or held check blocks instead of being waved past.
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Every major the auto-merge workflow held back ended the same way: the checks
were green, the release notes said nothing the tests had not already answered,
and a person pressed the button days later. The gate cost latency and bought
nothing, so it is gone: any Dependabot pull request now merges itself once
every check on the vetted commit is green — patch, minor and major alike.
What changed in
dependabot-auto-merge.yml:dependabot/fetch-metadataare removed — nothing needsthe update type any more, which is also one third-party action less in the
merge path. The commit vetting (all commits authored by
dependabot[bot],signed, merged with
--match-head-commit) is unchanged.no-automergelabel is the manual hold, replacingautomerge-ok, whichlabelled the common case instead of the exception. A run reads it at start;
the daily sweep respects it too.
check that is not this workflow's own has passed or been skipped, counted by
bucketrather thanstate, so a cancelled or held check keeps the pullrequest open. This also gives the workflow a defined answer on a repository
without branch protection.
labelled ones.
In settings, not in this diff: "require branches to be up to date" is switched
off for
main. A Dependabot branch cannot be brought up to date automatically(a
GITHUB_TOKENpush triggers no checks, and Dependabot ignores rebasecommands from bots), so the strict rule parked the second grouped update of
the week until Dependabot's next weekly run — today's stalled setup-uv bump
in browser-in-a-box was exactly that. The required checks themselves stay.