More on Merge conflicts #856
|
Can you show how merge conflicts look like?? |
Answered by
pasindupiumal
Sep 17, 2025
Replies: 2 comments 1 reply
|
sure i can cover this |
0 replies
|
🔹 How merge conflicts look in Git When a merge conflict happens, Git marks the conflicting lines in the file like this: Everything between <<<<<<< HEAD and ======= is your version. Everything between ======= and >>>>>>> feature-branch is the other branch’s version. 👉 You resolve it by editing the file, keeping the correct lines (or combining them), then saving and committing again. |
1 reply
Answer selected by
sanjay-kv
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@IOutis
🔹 How merge conflicts look in Git
When a merge conflict happens, Git marks the conflicting lines in the file like this:
Everything between <<<<<<< HEAD and ======= is your version.
Everything between ======= and >>>>>>> feature-branch is the other branch’s version.
👉 You resolve it by editing the file, keeping the correct lines (or combining them), then saving and committing again.