git rerere
Hacker ApprovedRanked 3 of 9 version control features by recommenders
Git's built-in cache that reuses your earlier conflict resolutions when the same conflict recurs, saving repeated fixes. Critics warn it can cache mistakes unnoticed.
Git's built-in cache that reuses your earlier conflict resolutions when the same conflict recurs, saving repeated fixes. Critics warn it can cache mistakes unnoticed.
23 people gave an opinion
- recommend it
- 19
- criticize it
- 4
- approval share
- 83%
Recommended in 8 of 13 months
- November 2025: recommended
- December 2025: recommended
- January 2026: recommended
- February 2026: not recommended
- March 2026: recommended
- April 2026: not recommended
- May 2026: not recommended
- June 2026: recommended
- July 2026: recommended
- August 2026: recommended
- September 2026: recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it carries the badge
- 19 people recommend itNeeds 10 or more, met.
- 4.8 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 8 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Resolves repeated conflicts automatically
“git rerere will resolve repeated conflicts for you automatically, you just need to enable it.”
Comment from 18 Aug 2026 in “Splitting a Git Commit” “rerere helps me by only having to fix the conflict once, not potentially multiple times”
Comment from 1 Jun 2026 in “Using Git's rerere feature to escape recurring conflict hell” “reduces the need to resolve the same conflict over and over”
Comment from 11 Nov 2025 in “The lazy Git UI you didn't know you need” - Comment from 23 Mar 2026 in “A Coherent Vision for the Future of Version Control”
Eases pain of repeated rebases
“rerere is still useful here to handle merge conflicts after repeated rebases.”
Comment from 1 Jun 2026 in “Using Git's rerere feature to escape recurring conflict hell” “`rerere` takes a lot of the pain out of layering rebased changes.”
Comment from 26 Jul 2026 in “Git rebase -I is not that scary” “git rerere would have saved me in the past”
Comment from 13 Jan 2026 in “Git Rebase for the Terrified” - Comment from 1 Jun 2026 in “Using Git's rerere feature to escape recurring conflict hell”
What people warn about
Each mark is one comment
Can cache mistakes and regressions
“it will also cache any mistakes in merging including things like bug regressions”
Comment from 18 Aug 2026 in “Splitting a Git Commit” “rerere cache problems are things that can go unnoticed for weeks to everyone's confusion”
Comment from 30 Dec 2025 in “Pre-commit hooks are fundamentally broken” Seen as unnecessary or counterproductive
“Rerere is dangerous and counterproductive - it tries to give rebase the same functionality that merge has”
Comment from 28 Jan 2026 in “I made my own Git” “tried rerere and didn't see the point”
Comment from 1 Jun 2026 in “Using Git's rerere feature to escape recurring conflict hell”
Other version control features people recommend
The four most recommended other version control features, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| Git worktree | 58 | 21 | 73% | 11 | — | Approved |
| git rebase | 24 | 13 | 65% | 9 | — | — |
| git rerereThis page | 19 | 4 | 83% | 8 | — | Approved |
| Git submodules | 14 | 13 | 52% | 7 | — | — |
| git add -p | 13 | 4 | 76% | 7 | — | Approved |
What people said
20 of the 25 comments that mention it, newest first. Each links to the original comment.
“it will also cache any mistakes in merging including things like bug regressions”
“git rerere will resolve repeated conflicts for you automatically, you just need to enable it.”
“It doesn't really fix the problem but it at least makes it less annoying.”
“`rerere` takes a lot of the pain out of layering rebased changes.”
“ReRe is pretty handy in those circumstances.”
“rerere helps me by only having to fix the conflict once, not potentially multiple times”
“tried rerere and didn't see the point”
“It not even work that much at the end”
“rerere is still useful here to handle merge conflicts after repeated rebases.”
“Git merge cache (git rerere) is good enough.”
“thanks to rerere git remembers the merge conflict resolution”
“Rerere is dangerous and counterproductive - it tries to give rebase the same functionality that merge has”
“it improves things enormously”
“the rebasing esperience was a hundred times worst”
“git rerere remembers the resolutions to the”
“rerere can help, but OP probably has their own workflow”
“git rerere would have saved me in the past”
“It's the solution to a lot of papercuts working with long-running branches as well as the source of new problems”
“rerere cache problems are things that can go unnoticed for weeks to everyone's confusion”
“reduces the need to resolve the same conflict over and over”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.