3 ms·
That justifies squashing inside a PR, but not making it linear. Commits might be coherently separated, eg: Commit 1: Add a user model Commit 2: Add migrations
by hobarrera 10y ago
That justifies squashing inside a PR, but not making it linear. Commits might be coherently separated, eg:
Commit 1: Add a user model
Commit 2: Add migrations for user model
Commit 3: Implement endpoints for users
Squashing them is pointless, and mixing them into a linear history really adds no value.
I do agree with squashing commits than cancel each other out inside a branch.