Skip to content

ci: fall back to a direct merge when auto-merge is refused #303

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
markuslf merged 1 commit into from
Aug 3, 2026
Merged

ci: fall back to a direct merge when auto-merge is refused #303

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion .github/workflows/dependabot-auto-merge.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,14 @@ jobs:
- if: >-
steps.meta.outputs.update-type == 'version-update:semver-patch'
|| steps.meta.outputs.update-type == 'version-update:semver-minor'
run: 'gh pr merge --auto --squash "$PR_URL"'
# `gh pr merge --auto` is refused while the pull request sits in clean or
# unstable state, which is exactly where a freshly opened Dependabot pull
# request lands once the required checks pass while the optional ones are
# still running. The direct merge is a safe fallback: branch protection
# keeps enforcing the required checks server-side, so a pull request that
# is not ready is still rejected.
run: |
gh pr merge --auto --squash "$PR_URL" || gh pr merge --squash "$PR_URL"
env:
PR_URL: '${{ github.event.pull_request.html_url }}'
GH_TOKEN: '${{ secrets.GITHUB_TOKEN }}'
Loading