ci: auto-merge green Dependabot PRs (minor/patch) - #121
Merged
Merged
Conversation
Enables GitHub native auto-merge for Dependabot PRs whose required checks all pass, holding major bumps for manual review. Uses the documented pull_request + explicit-permissions pattern with the automatic GITHUB_TOKEN — no PAT. fetch-metadata is SHA-pinned (repo requires it). 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.
Caveat 2 — replicates the LotteryApp auto-merge automation here.
Adds
.github/workflows/dependabot-auto-merge.yml: Dependabot PRs whose required checks all pass merge themselves (minor/patch; majors held for review). Branch protection still gates everything.GITHUB_TOKEN(documentedpull_request+ explicit-permissionspattern).dependabot/fetch-metadatais SHA-pinned (this repo enforces SHA-pinning).WidgetWorks doesn't use Central Package Management, so it has no lock-file (NU1004) problem — the LotteryApp lock-file-sync workflow isn't needed here.
🤖 Generated with Claude Code