3 ms·
I really doubt that it's ever necessary to understand the intricate history of each and every developer working on a codebase to be able to track regressions. Y
by globular-toast 6y ago
I really doubt that it's ever necessary to understand the intricate history of each and every developer working on a codebase to be able to track regressions. You're not Poirot.
History is an artifact of development and if it's worth keeping then it's worth maintaining. Rebasing serves to clean up the history ready for archiving (ie. merging to master), giving you a long linear line of commits that is possible to bisect to quickly find the source of regressions.
- kubanczyk 6y agoYep, architecture decision records (ADRs) for the win. Just next to your README file in the repo. But big projects seldom use rebase. This is because it's quite hard to `git revert` an entire change from two weeks before (change being e.g. 50 related commits).
- juped 6y agoYou do want to curate topics with interactive rebase, but you probably shouldn't want to destroy useful information by making everything linear. This is a common and I believe misguided thing people do when they don't know about e.g. gitk (which comes with Git, although your OS packager might split it out). It certainly doesn't aid the bisect command at all. It might hinder it (e.g., a whole series becomes bad because you rebased it off a release tag onto some random point; bisect would pinpoint the merge if you had merged it, but you destroyed useful information so it can only pinpoint one of the diffs). As you say, you definitely don't want to archive every weird developer fumble during development. That's useless noise that makes the history unreadable.