The Merge Button
With Pull Requests 2.0, it became easier than ever to review code and accept patches. We use pull requests extensively at GitHub, and I love receiving pull requests on my…
With Pull Requests 2.0, it became easier than ever to review code and accept patches. We use pull requests extensively at GitHub, and I love receiving pull requests on my open source projects.
Take, for example, this pull request for a documentation fix in God:
Traditionally, merging this pull request required multiple steps via the git command line. Not anymore!
All pull requests now include a Merge Button:
If a merge conflict is detected, the button is replaced with manual merge instructions:
A single click on the button automatically merges and closes the pull request:
The merge always generates a merge commit (git merge --no-ff), which contains the number, source and title of the pull request:
Try it out on some of your pull requests. Have fun merging!
Written by
Related posts
GitHub joins coalition advocating for fixes to California AI Transparency Act to protect open source
We’re calling for targeted amendments to resolve conflicts with open source licensing and align with international transparency frameworks while preserving regulatory intent.
GitHub availability report: May 2026
In May, we experienced nine incidents that resulted in degraded performance across GitHub services.
GitHub Universe is back: All together now, in the agentic era
GitHub Universe is back: returning to the historic Fort Mason Center in San Francisco on October 28–29, 2026.