More on Merge conflicts #856
-
Can you show how merge conflicts look like?? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
sure i can cover this |
Beta Was this translation helpful? Give feedback.
-
🔹 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. |
Beta Was this translation helpful? Give feedback.
@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.