Git Merge Conflicts

The cluster focuses on challenges with merge conflicts in Git, including debates on merge commits versus rebasing, strategies to avoid or resolve them, and their impact on development workflows.

➡️ Stable 0.5x DevOps & Infrastructure
4,055
Comments
20
Years Active
5
Top Authors
#4468
Topic ID

Activity Over Time

2007
3
2008
16
2009
46
2010
91
2011
147
2012
116
2013
154
2014
147
2015
228
2016
265
2017
183
2018
202
2019
195
2020
377
2021
317
2022
424
2023
376
2024
353
2025
381
2026
36

Keywords

GitLab MERGE MR e.g RelNote CI gitlab.com github.com ycombinator.com API merge merging conflicts rebase merged commits git conflict patches workflow

Sample Comments

nsfyn55 Nov 29, 2014 View on HN

I don't believe this will save you from the merge conflicts.

withinboredom Nov 20, 2022 View on HN

Sounds like that merge conflict would suck to resolve.

darepublic Oct 22, 2019 View on HN

This is not a guarantee of no merge conflicts. Sometimes conflict cannot be avoided, you'll need to deal with it sooner or later

dan-robertson Apr 12, 2020 View on HN

The hard part is merging different changes.

cryptonector Jan 13, 2026 View on HN

You'd have merge conflicts whether you merge or rebase.

erikb May 27, 2016 View on HN

Yes, and these can't be merged with git yet.

rlpb Jun 2, 2011 View on HN

I think that's better worded as "Merges can be hard". There isn't anything git-specific here.

lmm Jun 9, 2015 View on HN

If it's just a matter of "merging" couldn't you just merge those branches again? Or do you resolve conflicts on github or some such (something that's never fit my workflow but I can imagine others using it)?

glitchc Aug 19, 2022 View on HN

Wait till you have to deal with a merge conflict.

senfiaj Sep 18, 2023 View on HN

Yap, the merge issue is one of the worst nightmares for developers.