Skip to main content
  • 655 Accesses

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.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 34.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 44.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Authors

Rights and permissions

Reprints 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

Publish with us

Policies and ethics