Hacker News new | ask | show | jobs
by blowski 1683 days ago
On large monolithic repos with a lot of people committing features independently, rebase helps reduce the noise in the history. If you mostly work on small repos (e.g. microservices) or repos with few contributors, then it makes sense you haven't needed rebase.
1 comments

Not quite. We have a workflow to resolve conflict though. All needed is just git merge, git pull. You need workflow, not git rebase.
A lot of very smart people disagree with you.
Then you must have never used "git bisect"? Or only bisect on the first parent?