Learn why conflicts happen and how to resolve them.

Merge conflicts happen when two people make changes to the same file on GitHub—a common occurrence when you’re working with others. While resolving differences might involve some discussion, merge conflicts don’t have to be scary. This course guides you through the steps to finding the best merge conflict solution, so your team can keep building.

• Who is this for: New developers, new GitHub users, users new to Git, students, managers, teams.
• What you’ll learn: What merge conflicts are, how you resolve merge conflicts, how to reduce merge conflicts.
• What you’ll build: We’ll work with a short Markdown resume file in this course.
• Prerequisites: We recommend taking Introduction to GitHub prior to this course.
• How long: This course takes less than 30 minutes to complete.

In this course, you will:

1. Create a pull request
2. Resolve a merge conflict
3. Create a merge conflict
4. Merge your pull request

1. Right-click Start course and open the link in a new tab.
2. In the new tab, most of the prompts will automatically fill in for you.
   • For owner, choose your personal account or an organization to host the repository.
   • We recommend creating a public repository, as private repositories will use Actions minutes.
   • Scroll down and click the Create repository button at the bottom of the form.
3. After your new repository is created, wait about 20 seconds, then refresh the page. Follow the step-by-step instructions in the new repository’s README.

Get help: Post in our discussion board • Review the GitHub status page

© 2023 GitHub • Code of Conduct • MIT License