feat(commands): add babysit-dependabot-pr command#2123
Merged
Conversation
Add a rulesync command that shepherds a Dependabot dependency-bump PR to merge: verify the author is the genuine Dependabot bot (login/type/id), diagnose and resolve CI failures (preferring to exclude a single breaking bump out of a grouped update, with a tracking issue for the deliberate migration), get every check green, and merge. Co-Authored-By: Claude Opus 4.8 (1M context) <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
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.
Summary
Adds a new rulesync command,
babysit-dependabot-pr, that shepherds a Dependabot dependency-bump PR all the way to a clean merge.The command captures the workflow:
login = dependabot[bot],type = Bot,id = 49699333, GitHub's canonical Dependabot app user id), not justgh pr view --json author. Stop if it is not genuine.main, regenerate the lockfile surgically), let the remaining updates land, and file a separate tracking issue for the deliberate migration. Fix-forward and close-for-regeneration are documented as alternatives.--admin --merge, leaving a comment recording what happened.PR titles, branch names, and comment bodies are treated as untrusted data.
This generalizes the manual babysit of PR #2114 (js-yaml v5 excluded from the group bump; migration tracked in #2122).
Test plan
pnpm cicheckpasses (code + content; 6752 tests green).getoperation (valid frontmatter + body).