GitHub · Pull requests · Update branch · Checked October 27, 2026

GitHub: the Update branch button does not show on a pull request

If the repository setting to always suggest updating pull request branches is on, people with write permissions can always update a pull request's head branch from the pull request page when it is not up to date with the base branch. When it is off, updating is only available when the base branch requires branches to be up to date before merging and the branch is not up to date (GitHub's managing suggestions to update pull request branches, checked October 27, 2026).

Always suggest updating pull request branches   on: shown whenever behind
setting off                                     shown only when the rules require up to date
merge conflicts                                 resolve them first
protected head branch                           the button may not work
PUT /repos/{owner}/{repo}/pulls/{pull_number}/update-branch   merge
updatePullRequestBranch(updateMethod: REBASE)                 rebase

Why it is not there

The setting is off: without Always suggest updating pull request branches, the button shows only when the base branch requires an up-to-date branch. With the Strict setting (Require branches to be up to date before merging checked), the branch must be up to date before merging; with Loose, it does not have to be (GitHub's about protected branches).
Merge conflicts: you can update the branch from the pull request page when there are no merge conflicts and the branch is behind the base branch. Resolve the conflicts first (GitHub's keeping your pull request in sync with the base branch).
A protected head branch: you may not be able to use Update branch if the head branch of the pull request is a protected branch.
Nothing to bring in: the branch is not behind the base branch.

What to do

Turn the suggestion on: in the repository settings, under Pull Requests, select Always suggest updating pull request branches.
Choose merge or rebase: in the merge section, Update branch merges the base branch into the head branch; from its dropdown, Update with rebase, then Rebase branch, rebases your changes onto the latest base branch, without a merge commit.
From the REST API: PUT /repos/{owner}/{repo}/pulls/{pull_number}/update-branch merges HEAD from the base branch into the pull request branch. expected_head_sha must match the head, or the answer is 422 (GitHub's update a pull request branch; see why updating the branch was refused).
From GraphQL: updatePullRequestBranch merges or rebases; its updateMethod is MERGE or REBASE, and MERGE when omitted (GitHub's updatePullRequestBranch and PullRequestBranchUpdateMethod).
Or let a merge queue do it: a merge queue gives the same benefits as requiring up-to-date branches, but does not require the pull request author to update the branch and wait for status checks to finish before trying to merge (GitHub's about protected branches; see merge queues).

In IntelliJ IDEA: no Update branch, and no line for a branch that is behind

How the GitHub support built into IntelliJ IDEA handles a pull request whose branch is behind the base branch, in its source (checked October 31, 2026; IntelliJ IDEA: GraphQL files, GithubApiRequests.kt, GHPullRequestMergeStateStatus.kt, GHPRMergeabilityStateBuilder.kt, GHPRMergeabilityState.kt, CodeReviewDetailsStatusComponentFactory.kt):

No Update branch: none of its GraphQL files has updatePullRequestBranch, and none of its REST requests calls update-branch, so the IDE cannot update a pull request's branch on GitHub.
Behind is not shown: GitHub's mergeStateStatus BEHIND turns Merge… and Squash and Merge… off except for an admin (see why auto-merge was refused), but the state the IDE hands to the status panel has no field for it, so no line says that the branch is out of date.
Resolve, the IDE's own merge or rebase of the base branch (see merge conflicts), shows only when GitHub reports conflicts. For a branch that is only behind, update it with git and push, or use Update branch on GitHub.

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. It compares the pull request with its target branch itself, so it shows Update the branch whenever the target branch has commits the pull request does not have and the two do not conflict, whether or not the repository suggests it; when the rules require an up-to-date branch, its merge checks say the rules ask for the new commits first. It updates by merging, through the REST API, and does not rebase. On a pull request Dependabot opened it says to comment @dependabot rebase instead. The review inbox, diffs and conversations are free; approving, commenting, resolving, merging and updating the branch 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.