GitHub: Dependabot does not rebase its pull request
By default, Dependabot automatically rebases its pull requests to resolve any conflicts. It stops rebasing a pull request once extra commits have been pushed to it, and one that has not been merged for 30 days; you can still rebase and merge it yourself, or ask Dependabot with a comment (GitHub's managing pull requests for dependency updates, checked October 27, 2026).
@dependabot rebase @dependabot recreate
Why Dependabot stopped rebasing
- Extra commits: by default Dependabot stops rebasing a pull request once extra commits have been pushed to it. Update branch is one way they get there: it merges the head of the base branch into the pull request branch (GitHub's update a pull request branch). Conflicts resolved by hand and pushed are another.
- 30 days: Dependabot stops rebasing a pull request that has not been merged for 30 days.
- The setting: with
rebase-strategy: disabledindependabot.yml, Dependabot stops rebasing its pull requests. Those open before you disabled it are still rebased until 30 days after they were opened (GitHub's Dependabot options reference). - When it looks: Dependabot checks for changes when the schedule for version updates runs, when you reopen a closed Dependabot pull request, when you change
target-branch, and when a Dependabot pull request is in conflict after a recent push to the target branch.
The comment commands
@dependabot rebase: rebases the pull request. Dependabot reacts with a thumbs up to acknowledge a command and may reply with a comment; when it is busy with other updates or commands, a command can take several minutes (GitHub's Dependabot pull request comment commands).@dependabot recreate: recreates the pull request, overwriting any edits that have been made to it.- Letting it force push: a commit whose message contains
[dependabot skip],[skip dependabot],[dependabot-skip]or[skip-dependabot], in lower or uppercase, does not stop Dependabot: it may rebase and force push over it. - Ignoring closes it:
@dependabot ignore this dependency, and the major, minor and patch version variants, close the pull request and store the preference for the repository centrally; with more than one contributor, GitHub suggests theignoreoption in the configuration file instead.
Other Dependabot pull request errors
- Already applied: Dependabot closes its pull request once the update has been committed to the default branch, but in rare cases it stays open.
@dependabot recreateor@dependabot rebasemakes Dependabot check, and close it when it is no longer required (GitHub's Dependabot errors). - An open pull request for the latest version: for a security update, Dependabot does not open a second pull request for a dependency that already has one open to its latest version. Merge that one when it is safe, or close it and trigger a new one.
- The limit: "Dependabot cannot open any more pull requests" when 10 security update or 5 version update pull requests are open (the second is
open-pull-requests-limit). Merge or close some, then trigger a new one. - Triggering one: for a security update, open the Dependabot alert and click Create Dependabot security update; for version updates, go to Insights, Dependency graph, the Dependabot tab, click Last checked TIME ago, then Check for updates.
What to do
- Behind or in conflict: comment
@dependabot rebaserather than updating the branch or resolving the conflicts yourself, which adds the commits that stop Dependabot. For other pull requests, see merge conflicts and updating the branch. - Someone already pushed to it:
@dependabot recreatestarts it over without those edits, or rebase and merge it yourself. - Keeping it rebased: leave
rebase-strategyat its default, and merge Dependabot pull requests within 30 days.
GitHub pull requests in IntelliJ IDEA
Pull Request Inbox for GitHub, a plugin by Lesstep for JetBrains IDEs 2024.1 or later, shows a pull request's reviews, checks and conversations next to the diff, and merges it with the methods the target branch allows. On a pull request Dependabot opened, its merge checks say to comment @dependabot rebase when the target branch has new commits or the two conflict, and it does not offer Update the branch there; its comment box sends the command from the IDE. The review inbox, diffs and conversations are free; approving, commenting, resolving and merging are Pro (US$1.50 a month, with a 30-day trial).
GitHub is a trademark of GitHub, Inc.; IntelliJ IDEA is a trademark of JetBrains s.r.o. This page is not affiliated with or endorsed by GitHub, Inc. or JetBrains.
More: GitHub merge refused (405, 409) · GitHub review refused (422) · GitHub search 422 "Validation Failed" · "Resource not accessible by personal access token" · 401 "Bad credentials" · "Resource protected by organization SAML enforcement" · "API rate limit exceeded" · GitHub diff 406 "too_large", 3,000 files · GitHub line comment 422 "must be part of the diff" · GitHub branch update refused (422) · GitHub pull request not created (422, 403) · GitHub auto-merge refused · GitHub draft, ready for review or close refused · GitHub conversation not resolved · GitHub checks not shown (check runs 403) · GitHub file contents not read · GitHub compare refused (404, 422) · GitHub comment or reply refused (403 locked, archived) · GitHub merge method not allowed (405) · GitHub branch not found (404, 301) · GitHub Enterprise Server not reached · GitHub review request not shown · GitHub pull request list incomplete · GitHub 404 Not Found, renamed repositories (301, 307) · GitHub line comment outdated or not on the diff · GitHub pull requests not updating, notifications late · GitHub suggested change cannot be applied · GitHub required check stuck at "Expected" · GitHub code owner review required · GitHub merge blocked by unresolved conversations · GitHub merge blocked by unsigned commits · GitHub branch that merges through a merge queue · GitHub merge waiting for an approval of the most recent push · GitHub merge waiting for code scanning results · GitHub merge waiting for code quality results · GitHub merge blocked by a code coverage threshold · GitHub merge blocked by license compliance results · GitHub branch locked or its updates restricted · GitHub branch not deleted after merging · GitHub merge waiting for a team's approval (Required reviewers) · GitHub merge blocked by secret scanning alerts · GitHub stacked pull request not merging · GitHub push blocked by push rules · GitHub merge blocked by commit metadata rules · GitHub force push blocked · GitHub issue not closed by a merged pull request · GitHub pull request not checked out locally · GitHub pull request has merge conflicts · GitHub changes requested and dismissing a review · GitHub co-author not credited for a commit · GitHub dependency review check failed · GitHub fork not syncing with upstream · GitHub pull request base branch not changing · GitHub pull request not reverting · GitHub pull request template not showing · GitHub pull request labels or assignees not added · GitHub pull request not closing or reopening · GitHub push blocked by push protection · GitHub pull request comment hidden · GitHub pull request blocked until deployments succeed · GitHub team review request replaced by members · GitHub pull request file no longer marked Viewed · GitHub pull request marked merged without being merged · GitHub Copilot review does not count as an approval · GitHub checks not running on a pull request a workflow created · GitHub Update branch button not shown on a pull request · GitHub checks failing on a Dependabot pull request · GitHub checks failing on a pull request from a fork · GitHub checks skipped by [skip ci] in a commit message · GitHub checks gone after the retention period · GitHub code review limits in a public repository · GitHub pull requests turned off or limited in a repository · GitHub checks run on every pull request in a stack · GitHub pull request showing commits already squash merged · GitHub pull request not showing a file diff · GitHub push to a pull request branch from a fork refused · GitHub check cancelled on a pull request · GitHub Rebase and merge not available · GitHub merge commit message not what you expected · GitHub pull request shows every line changed · GitHub API request timed out · GitHub pull request image or document diff not shown · GitHub review request refused (422) · GitHub pull request from Copilot: checks not running, approval not counted · GitHub push refused: GH006 and GH013 on a protected branch · GitHub "At least 1 approving review is required", approvals that do not count · GitHub pull request plugins for IntelliJ IDEA, compared · 日本語