3 ms·

The most important benefit of preserving the history is being able to go to an exact state of the program in the past. Pinpointing the commit that introduced a

The most important benefit of preserving the history is being able to go to an exact state of the program in the past. Pinpointing the commit that introduced a regression is often by far the quickest method to localize the problem. And it is impossible when the history is rewritten, and consists of snapshots that were never even ran. This benefit is much more important than having a visually pleasing history. And you can always get a visually pleasing history by adding a few flags to git log.

TomSwirly 5y ago
> The most important benefit of preserving the history is being able to go to an exact state of the program in the past. No one's talking about ever getting rid of any commit ID that got checked into `main` or `master`. We're talking about getting rid of commit IDs that only ever existed on one machine and only during development. From my reflog, I see this commit ID: `21b9f2e HEAD@{28}: commit: Fix and instrument nstray URL problem` No one needs to know about my typo - ever.