Interview Q&A / Git & GitHub

BeginnerQuick answer1 min readUpdated 3 Oct 2026

Can you resolve a merge conflict on GitHub without using the command line?

SHORT ANSWER

Yes for simple text conflicts. The pull request page has a Resolve conflicts button that opens an editor with markers; fix them, mark resolved and commit. Complex cases like deleted or binary files need a local merge.

Explain it simply

Handy when you are on a mobile browser with no laptop: GitHub offers a web editor for conflicts.

On the pull request, click Resolve conflicts. GitHub shows each file with the familiar markers. Edit the text, click Mark as resolved, then Commit merge. That adds a merge commit to the PR branch. The button is unavailable when the conflict involves binary files, renamed and deleted files together, or the changes are too large. For those, merge the base branch locally, fix, and push.

Example

text
Pull request page
  This branch has conflicts that must be resolved
  [Resolve conflicts]  ->  edit  ->  [Mark as resolved]  ->  [Commit merge]

What to say in the interview

"GitHub's web editor can resolve simple text conflicts: Resolve conflicts, edit the markers, mark resolved and commit the merge. For binary files or complex rename and delete conflicts I merge the base branch locally."

#github#conflicts#pull-request

Related questions

Practise more Git & GitHub questions

Test your recall with short answers, then return to the detailed explanations when you need context.

Open Git & GitHub quick answers →

Get new questions like this by email

One short email when something new and useful lands. No spam, unsubscribe in one tap.

By subscribing you agree to the Privacy Policy.