Resolving merge conflicts in Git - Time & Space Complexity

Time Complexity: Resolving merge conflicts

O(n)

Understanding Time Complexity

When merging branches in git, conflicts can happen if changes overlap. Understanding how the time to resolve conflicts grows helps us plan better.

We want to know: how does the effort to fix conflicts change as the conflicting changes grow?

Scenario Under Consideration

Analyze the time complexity of resolving conflicts after a merge attempt.

git checkout feature-branch
git merge main
# If conflicts appear, open files and edit conflict markers
# After fixing, run:
git add <fixed-files>
git commit -m "Resolve merge conflicts"

This snippet shows the steps to merge and resolve conflicts manually.

Identify Repeating Operations

Look for repeated work when resolving conflicts.

• Primary operation: Manually reviewing and editing each conflicting file.
• How many times: Once per conflicting file, and within each file, per conflicting section.

How Execution Grows With Input

The time to resolve conflicts grows with the number of conflicting files and conflict sections inside them.

Input Size (conflicts)	Approx. Operations (edits)
10 conflict sections	10 edits
100 conflict sections	100 edits
1000 conflict sections	1000 edits

Pattern observation: The effort grows roughly in direct proportion to the number of conflicts.

Final Time Complexity

Time Complexity: O(n)

This means the time to resolve conflicts grows linearly with the number of conflicting sections you must fix.

Common Mistake

[X] Wrong: "Resolving one conflict fixes all conflicts automatically."

[OK] Correct: Each conflict is separate and must be fixed manually; fixing one does not solve others.

Interview Connect

Understanding how conflict resolution scales shows you can manage code changes smoothly and keep projects moving forward.

Self-Check

"What if we used a merge tool that automatically resolves some conflicts? How would the time complexity change?"

Practice

1. What does a merge conflict in Git mean?

easy

A. Git found changes in the same file that it cannot combine automatically.

B. Git has successfully merged all changes without any issues.

C. Git deleted a file during the merge process.

D. Git created a new branch automatically.

Solution

1. Step 1: Understand merge conflict meaning

   A merge conflict happens when Git sees changes in the same part of a file from different branches and cannot decide which to keep.

2. Step 2: Identify what Git does in this case

   Git stops the merge and marks the conflict in the file for you to fix manually.

3. Final Answer:

   Git found changes in the same file that it cannot combine automatically. -> Option A

4. Quick Check:

   Merge conflict = conflicting changes in same file [OK]

Hint: Merge conflict means manual fix needed for overlapping changes [OK]

Common Mistakes:

• Thinking Git merges all changes automatically
• Confusing conflict with branch creation
• Assuming files are deleted automatically

2. Which Git command is used to mark a conflict as resolved after editing the file?

easy

A. git add <file>

B. git commit -m 'resolve conflict'

C. git merge --continue

D. git checkout --conflict

Solution

1. Step 1: Identify how to tell Git conflict is fixed

   After editing the conflicted file, you must stage it to tell Git the conflict is resolved.

2. Step 2: Choose the correct command to stage files

   The command to stage files is git add <file>.

3. Final Answer:

   git add <file> -> Option A

4. Quick Check:

   Stage resolved file with git add [OK]

Hint: Use git add to mark conflict resolved before commit [OK]

Common Mistakes:

• Trying to commit before staging resolved files
• Using git merge --continue without staging
• Using invalid commands like git checkout --conflict

3. Given this conflict marker in a file after a merge:

<<<<<<< HEAD
Line A
=======
Line B
>>>>>>> feature-branch

What will the file content be after you keep only the changes from the feature-branch and stage the file?

medium

A. Line A

B. Line B

C. <<<<<<< HEAD
Line A
=======
Line B
>>>>>>> feature-branch

D. Line A
Line B

Solution

1. Step 1: Understand conflict markers

   The lines between <<<<<<< HEAD and ======= are from current branch; lines between ======= and >>>>>>> feature-branch are from the other branch.

2. Step 2: Keep only feature-branch changes

   To keep only feature-branch changes, remove the markers and the HEAD section, leaving just 'Line B'.

3. Final Answer:

   Line B -> Option B

4. Quick Check:

   Keep feature-branch changes = Line B [OK]

Hint: Remove conflict markers, keep desired lines, then git add [OK]

Common Mistakes:

• Leaving conflict markers in file
• Keeping both changes without cleaning markers
• Confusing which side is which branch

4. You tried to merge a branch but Git reports conflicts. You edited the files but forgot to stage them before committing. What happens if you run git commit now?

medium

A. Git commits the merge with unresolved conflicts included.

B. Git automatically stages and commits the resolved files.

C. Git refuses to commit and shows an error about unmerged paths.

D. Git aborts the merge and resets to previous state.

Solution

1. Step 1: Understand commit behavior during merge conflicts

   Git requires you to stage resolved files before committing a merge. If files are not staged, Git sees conflicts as unresolved.

2. Step 2: What happens when committing without staging

   Git will refuse to commit and show an error about unmerged paths, preventing incomplete merges.

3. Final Answer:

   Git refuses to commit and shows an error about unmerged paths. -> Option C

4. Quick Check:

   Commit without staging resolved files = error [OK]

Hint: Always git add resolved files before git commit [OK]

Common Mistakes:

• Assuming git commit auto-stages files
• Thinking Git commits partial merges
• Expecting merge to abort automatically

5. You have a file with multiple merge conflicts from two branches. You want to keep all changes from both branches but Git shows conflicts. What is the best way to resolve this?

hard

A. Run git reset --hard to discard all changes and merge again.

B. Use git merge --abort to cancel the merge and try again.

C. Delete the file and create a new one with combined content.

D. Manually edit the file to combine both changes, remove conflict markers, then stage and commit.

Solution

1. Step 1: Understand the goal to keep all changes

   Since you want to keep both branches' changes, you must manually combine them in the file.

2. Step 2: How to resolve conflicts properly

   Edit the file to merge both changes, remove conflict markers, then stage with git add and commit the merge.

3. Final Answer:

   Manually edit the file to combine both changes, remove conflict markers, then stage and commit. -> Option D

4. Quick Check:

   Manual merge + stage + commit = keep all changes [OK]

Hint: Edit conflicts to combine changes, then git add and commit [OK]

Common Mistakes:

• Aborting merge instead of resolving
• Deleting files losing changes
• Resetting hard losing all work