Bird
0
0

You have a project where the same conflict happens often between two branches. How can you use rerere to save time and avoid repeated manual fixes? Choose the best approach.

hard📝 Workflow Q15 of 15
Git - Cherry-Pick and Advanced Merging
You have a project where the same conflict happens often between two branches. How can you use rerere to save time and avoid repeated manual fixes? Choose the best approach.
ARun <code>git rerere clear</code> before every merge to reset conflict history.
BDisable rerere and always resolve conflicts manually to avoid mistakes.
CUse rerere only on one branch and manually copy resolutions to the other branch.
DEnable rerere globally, resolve the conflict once and commit, then rerere will auto-apply fixes on future merges.
Step-by-Step Solution
Solution:
  1. Step 1: Enable rerere globally for all repositories

    This ensures rerere is active and can record conflict resolutions anywhere.
  2. Step 2: Resolve the conflict once and commit the fix

    Rerere records this resolution to reuse it automatically on repeated conflicts.
  3. Step 3: Benefit from rerere auto-applying fixes on future merges

    This saves time by avoiding repeated manual conflict resolution.
  4. Final Answer:

    Enable rerere globally, resolve the conflict once and commit, then rerere will auto-apply fixes on future merges. -> Option D
  5. Quick Check:

    Enable + commit fix = rerere auto-applies [OK]
Quick Trick: Enable rerere, commit fix once, future merges auto-fix [OK]
Common Mistakes:
  • Disabling rerere loses automation benefits
  • Using rerere only on one branch misses conflicts
  • Clearing rerere history removes saved fixes

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Git Quizzes