Abstract
Before I go into anything major in this chapter, I need to cover what conflicts are and how they happen. On the basic level, a conflict occurs when two people are working on the same part of a file at the same time. When the first user commits their code, that commit is fine, because there are no changes to conflict with it. However, when the second user goes to update, then there is a problem. When the versioning system tries to merge the files together, the changes from both users are new and in the same location, so the versioning system gets confused about what goes where; as a result, it creates a conflicted file containing both sets of changes. Conflicts commonly happen when more than one person makes a change to, for instance, a width value in CSS. Since the system doesn’t know which value it should use, it gets confused and conflicts the file.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Rights and permissions
Copyright information
© 2012 Chris Kemper and Ian Oxley
About this chapter
Cite this chapter
Kemper, C., Oxley, I. (2012). I Have a Conflict: What Can I Do?. In: Foundation Version Control for Web Developers. Apress. https://doi.org/10.1007/978-1-4302-3973-4_8
Download citation
DOI: https://doi.org/10.1007/978-1-4302-3973-4_8
Publisher Name: Apress
Print ISBN: 978-1-4302-3972-7
Online ISBN: 978-1-4302-3973-4
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books