ci: merge dependabot PRs once CI has passed on them - #249
Merged
Conversation
Not GitHub's own auto-merge: that needs `allow_auto_merge` on the repo and, to be worth anything, required status checks on main. This repo has neither, and with no required checks GitHub's auto-merge merges immediately rather than waiting for CI. Triggering on `workflow_run` makes "CI finished and it was green" the entry condition instead. Two updates stay with a person: escapepod-signal, whose PyPI twin has to move in the same commit, and any major bump, where CI passing means the suite still runs rather than that the semantics held. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CdbVo6UnMuYNmt2D7tjT3B
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.
Merges a dependabot PR once CI has actually passed on it.
Not GitHub's native auto-merge. That needs
allow_auto_mergeon the repoand, to be worth anything, required status checks on
main. This repo hasneither —
allow_auto_mergeisfalseandmainis unprotected — and with norequired checks GitHub's auto-merge merges immediately rather than waiting for
CI, which is worse than merging by hand. Triggering on
workflow_runinsteadmakes "CI finished and it was green" the entry condition by construction, and
needs no repo-settings change.
What stays manual
escapepod-signalescapepodmust move in the same commit. Merging the crate alone putsmainin exactly the skewescapepod-sync.ymlthen has to repair (#193).Everything else — patch and minor, dev tooling and runtime alike — merges on
green. Note this lets 0.x minor bumps through (
0.14 → 0.15), which arebreaking by convention; the alternative held back most dependabot traffic and
defeated the point. Two-line change if you'd rather be strict.
Verification
The title parse is the part that can silently misfire, so it was checked
against this repo's real titles — including
bump escapepod-signal from v0.16.1 to v0.18.1 in /rust, whose trailingin /rustandvprefix both have tosurvive — plus major bumps, a major on a held-back dep, and a non-bump title
that must fail closed. 8 cases, all passing.
Also corrects a now-inaccurate comment in
escapepod-sync.yml: it claimeduv.lockpredates the emscripten markers, which stopped being true whenuv sync --upgradenormalized the lock.🤖 Generated with Claude Code
https://claude.ai/code/session_01CdbVo6UnMuYNmt2D7tjT3B