✳flâneur — a map of the web's best reading

Resolve Git conflicts | WebStorm Documentation

jetbrains.com · 1,311 words · saved by 1 readers

When you work in a team, you may come across a situation when somebody pushes changes to a file you are currently working on. If these changes do not overlap (that is, changes were made to different lines of code), the conflicting files are merged automatically. However, if the same lines were affected, Git cannot randomly pick one side over the other, and asks you to resolve the conflict. In Git, conflicts may arise when you attempt to perform one of the following operations: pull, merge, rebase, cherry-pick, unstash changes or apply a patch. If there are conflicts, these operations will fail, and you will be prompted to accept the upstream version, prefer your version, or merge the changes: The Conflicts dialog is triggered automatically when a conflict is detected on the Git level. If you click Close in this dialog, or call a Git operation that leads to a merge conflict from command line, a Merge Conflicts node will appear in the Local Changes view with a link to resolve them: WebSt

Resolve Git conflicts When you work in a team, you may come across a situation when somebody pushes changes to a file you are currently working on. If these changes do not overlap (that is, changes were made to different lines of code), the conflicting files are merged automatically. However, if the same lines were affected, Git cannot randomly pick one side over the other, and asks you to resolve the conflict. In Git, conflicts may arise when you attempt to perform one of the following operations: pull , merge , rebase , cherry-pick , unstash changes or apply a patch . If there are conflicts,

Explore this link on the map →

related reading