This is a fantastic update, the one-click conflict resolution is a real time-saver! Having Accept incoming/current/both changes directly in the web interface makes quick fixes much smoother, especially for smaller teams or when working on mobile.

OMG, I’ve been waiting for this forever! Resolving conflicts on the web will be so much easier now.

This is a really nice update! 🎉
Being able to fix merge conflicts right in the browser makes work faster, especially for small or quick edits.
It’s a great improvement for developers who want to merge quickly and safely. Thanks to the team for adding this! 🙌

This is the feature I have been needed for long time! 🎉

However, I want one more tiny addition to this feature: "Accept both changes in reverse order".
When writing changelog, I only want to append new feature to bottom rather than inserting in between entries.
The current "Apply both changes" will apply head branch changes first and base branch later, but I want to apply base branch first.

We need blame information about who has caused a conflict for this to be really useful with larger teams! :)

You can now resolve merge conflicts directly in the github.com web interface with a single click! 🎉

When a pull request has merge conflicts that can be resolved in the web interface, you’ll see new Accept incoming changes, Accept current changes, and Accept both changes buttons in the web editor. These actions, familiar to users of code editors like Visual Studio Code, make it easier and faster to resolve conflicts without leaving your browser.

### How does it work? When a PR has merge conflicts, you’ll see clear conflict markers and the new one-click resolution buttons.

• Accept current changes keeps the changes from the current working branch.
• Accept incoming changes uses the changes from the base branch.
• Accept both changes combines both sets of changes in the file.

This update brings the productivity and convenience of popular code editors’ merge tools directly to your github.com workflow—no context switching required.

How you can help

If you run into issues or have any feedback, feel free to drop a comment in this post. We'd love to get your feedback!