

0 / 2 embers
0 / 3000 xp
click for more info
Complete a lesson to start your streak
click for more info
Still calibrating
click for more info
Not enough gems
Cost: 6 gems
1: Conflicting Changes
incomplete
2: Merge Conflicts
incomplete
3: Merge
incomplete
4: Edit the File
incomplete
5: Resolution
incomplete
6: Conflict Quiz
incomplete
7: Back to Main
incomplete
8: Back to Main
incomplete
9: Ours and Theirs
incomplete
10: Multi-conflict
incomplete
11: Checkout Conflict
incomplete
12: No Merge Commits
incomplete
Back
ctrl+,
Next
ctrl+.
This lesson's interactive features are locked, please to keep using them
Resolving conflicts is a manual process. When they happen, Git marks the conflicted files and asks you to resolve the conflict by editing the files in your editor.
You should see a nasty bit of text that looks like this:
first_name,last_name,company,title
<<<<<<< HEAD
karson,yummy,intercooler,ceo
=======
jayson,gross,htmz,contributor
>>>>>>> main
Your editor might even highlight the conflict markers to make it easier to see, but at the end of the day, it's just text. The top section, between the <<<<<<< HEAD and ======= lines, is our branch's version of the file. The bottom section, between the ======= and >>>>>>> main lines, is the version of the file that's on the main branch ("theirs" or as I say "Stupid Greg's").
In many cases, you might want to keep one change and discard the other. That's common when you're dealing with code changes. In this case, we're dealing with content, so we want to keep both changes.
The file should look like this:
first_name,last_name,company,title
karson,yummy,intercooler,ceo
jayson,gross,htmz,contributor
Run and submit the CLI tests from the root of the repo.