update branch button broken since March 3rd, 2026

[ReenigneArcher]

Select Topic Area

Bug

Body

The update branch button is broken (sometimes) since March 3, 2026.

It now always looks like the following:

There used to be a dropdown menu, where we could select how to update the branch.

In both of these repos I have this option enabled.

I personally hate the "merge commit" option. Please fix.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[axelson]

I don't see anything in the changelog about this and the help docs still show a "Update with rebase" option (https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch#updating-your-pull-request-branch):

[opti]

Might be related to that feature: https://github.blog/changelog/2026-03-05-quick-access-to-merge-status-in-pull-requests-in-public-preview/

[scrousenator]

day 3 of this. Please. I'm suffering.

[ebndev]

Hi all, thanks for taking the time to report this and for your patience!

The GitHub team is aware of this and they are working on a solution.

I'll report back when we have more updates!

[modosc]

we have a support ticket opened on this. we were advised that the only way to enable rebasing of prs now is to allow rebase merging:

I spoke with my engineers here, and they advised this is expected behavior as of some changes we made recently.

Before this setting did not determine the updating of the branch button, but now it does. So in order for this to be utilized this setting must be enabled.

the ticket was then closed as completed two hours ago.

i'm commenting here because there seems to be some disconnect between the support response and @ebndev 's response above. does github consider this a regression or a feature?

[skalteis]

I guess there might be more users who rebase PR branches but then squash merge to base branch? Why did they see a need to remove a perfectly fine option (I would even go as far as suggesting to introduce the option to be able to specify how PR branches should be updated by default)?

[broksonic21]

That's exactly what our team does and why this is really impacting us.

Squash -> Main
But often rebase in a PR

Same as what @mbranch mentions below for their workflow.

[mbranch]

At my org, we only allow squashing to merge to enforce 1 pull request => 1 commit on main. However, in long running pull requests with feedback and additional commits, being able to rebase main from the Github UI is valuable even though we don't want to enable rebase merges (1 pull request => potentially n commits on main).

[scrousenator]

Exactly. I have a have a hard time believing this general workflow slipped through the cracks when this feature was scrubbed, it must be unintentional.

[modosc]

another update from support:

In this case this is expected as of the latest change our engineers updated to the site.

I have let our engineers know of your feedback, and this public discussion as well. I cannot say if or when they may roll this back based on this feedback.

At this time, this has been confirmed working as expected.

I'll go ahead and mark this ticket as Solved, as there is no further action on behalf of support.

apparently we've all been using it wrong.

[davidxia]

I don't have "Allow rebase merging" enabled.

But the "Update with rebase" has re-appeared for me.

huh?

[modosc]

it just started working for us as well, maybe this thread helped.

[ReenigneArcher]

I can also report the original behavior is back. Hopefully it stays that way.

The setting clearly states that it applies to "merging pull requests". Definitely should not affect how you update a PR branch.

[davidxia]

"Update with rebase" option is restored. But trying to do so always results in error "Rebase conflict between head and base." even when there are no conflicts. I resort to rebasing and force pushing myself. Anyone else encounter this?

[modosc]

we are as well.

[jesseduffield]

I get this too. So that others can find this issue via google I'll paste the text content of that error here:

Rebase conflict between head and base.

[serkansahin]

Hey guys,

I have described a workaround in this thread https://github.com/orgs/community/discussions/188709, it is not a viable solution but hope it works for you too.

[beaugunderson]

broken for us as well in all our repositories

[oualeo]

Reported in https://github.com/orgs/community/discussions/189197