Closed github-learning-lab[bot] closed 3 years ago
In a real world scenario, it's possible that a peer or colleague will have edited the same file in the same place as your pull request.
To demonstrate, I'll stand in as your colleague :wave:. In this other pull request https://github.com/MJPritzl/merge-conflicts/pull/2, you'll see that the education file has been changed. The other pull request was just merged to main
, which means there's now a conflict in your pull request.
Because you created the conflict, feel free to resolve this conflict as you wish.
Great job, @MJPritzl, your pull request is free of conflicts. :tada: Go ahead and merge this pull request now.
Yay! You've done it! You've resolved all of the conflicts. I have a few pointers for completing your resume, so I've opened one last issue for that information.
Step 5: Create your own conflict
So far, this pull request doesn't have any conflicts. I have added some new branch protections to prevent you from merging before you're ready.
In the last activity, you solved a merge conflict that someone else created. This time, you'll create the merge conflict yourself.
:keyboard: Activity: Make changes on this branch
_data/education.yml
file that had been previously modified.degree:
,uni:
,year:
, andsummary:
lines.Watch below for my response.