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

From MCP to multi-agents: The top 10 new open source AI projects on GitHub right now and why they matter
Get insights on the latest trends from GitHub experts while catching up on these exciting new projects.

Racing into 2025 with new GitHub Innovation Graph data
Discover the latest trends and insights on public software development activity on GitHub with the quarterly release of data for the Innovation Graph, updated through December 2024.

GitHub Availability Report: March 2025
In March, we experienced one incident that resulted in degraded performance across GitHub services.