3 ms·
why would you squash multiple informative commits with their commit messages and their informative context about your thought process into a single big squashed
by aulin 4y ago
why would you squash multiple informative commits with their commit messages and their informative context about your thought process into a single big squashed commit? git can merge branches and keep track of it, there is no need to squash unless you split trivial changes that belong together and want to group them before sharing them
- theonething 4y ago> no need to squash unless you split trivial changes that belong together If a PR represents a distinct product feature/bug fix/unit of work, one could argue that its commits belong together. Squashing makes for a very clean history. True it reduces granularity, but in my opinion at least, it's a good level of granularity. The exception to this would be a really big PR. That's a reason to avoid huge PRs.