Just like your first conflict, this pull request is already conflicted.
This time, however, I've made it a bit more complicated.
Instead of one conflict, you get three!
Instead of conflicts in one file only, you get two!
One of your files actually has some leftover merge conflict markers. This can happen if someone forgets to remove the markers while resolving a conflict.
:keyboard: Activity: Resolve these conflicts
Click Resolve conflicts.
On the left, you will notice two files listed: _data/experience.yml and _data/interests.yml. Let's start with _data/experience.yml.
Remove the conflict markers and pick your desired content.
With the merge conflicts resolved and the markers removed in the _data/experience.yml file, click Mark as resolved.
GitHub will present the next file with conflicts, _data/interests.yml.
Remove the conflict markers and pick your desired content.
Step 3: Resolve more complex conflicts
Just like your first conflict, this pull request is already conflicted.
This time, however, I've made it a bit more complicated.
:keyboard: Activity: Resolve these conflicts
_data/experience.yml
and_data/interests.yml
. Let's start with_data/experience.yml
._data/experience.yml
file, click Mark as resolved._data/interests.yml
.Watch below for my response.