Post #1812451
2026-04-30 08:26 UTC
I’m not a fan of changing history in general. Rebase can also he dangerous.
I think ultimately it’s a matter of scale. Sometimes it can be useful to look into the details of the development of a single feature, but in a large project, that rarely happens. I’m not a fan of squashing, but for large projects, it helps to keep your history manageable.
Replies (1)
-
@expr@piefed.social 2026-04-30 13:08
Rebasing is not dangerous. You can always go back if something is not to your liking. You don’t rebase shared history, you use rebases to craft a clean, quality commit history for your own branches before merging. If everyone does this, then squashing is unnecessary, because garbage commits don’t exist. It is the far superior way of doing things if you actually care about having good commits. Keeping a quality history rather than squashing also makes many other git tools much better, such as git blame, git revert, git bisect, and so on.