Merge Conflict: When Git can’t combine two changes automatically because both edited the same lines, so a person has to decide what the final code should be.
Example
You and a teammate both changed the same function, so Git shows a conflict when you merge.
Why Merge Conflict matters for IT interns
Conflicts are normal, not a disaster. Resolve them carefully, and ask the other person if you aren’t sure which change is right.
Where you will hear it
You will use this term almost daily when working on code with a team, through Git, GitHub, or a similar tool. If someone uses it and you are not sure what they mean in your project, it is completely fine to ask; every team uses terms a little differently.
Related terms
- GitHub: A website that stores Git repositories online and adds team features like Pull Requests, code review and…
- Main Branch: The primary branch of a repository, holding the stable, accepted code.
- Merge: Combining the changes from one branch into another.
- Pull: Bringing the latest changes from the shared remote repository into your local copy.
- Pull Request (PR): A Pull Request is a request to merge your code changes from one branch into another branch, usually after…
- Push: Sending your local commits to the shared remote repository so others can see them.
Previous term: Merge | Next term: Microsoft Azure
Related guides
Frequently asked questions
What is Merge Conflict?
When Git can’t combine two changes automatically because both edited the same lines, so a person has to decide what the final code should be.
What is an example of Merge Conflict?
You and a teammate both changed the same function, so Git shows a conflict when you merge.
Why does Merge Conflict matter for IT interns?
Conflicts are normal, not a disaster. Resolve them carefully, and ask the other person if you aren’t sure which change is right.
Explore more internship terms
The IT Internship Glossary explains 199 terms you will hear before and during your internship, with simple definitions and real examples.
Browse all 199 terms