I used to do that but these days I prefer the whole story be in there so I can r... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		jaggederest on Oct 25, 2023 \| parent \| context \| favorite \| on: Unified versus Split Diff I used to do that but these days I prefer the whole story be in there so I can reference it later if I run into the same bug in a different place. In general I find my past efforts to maintain a clean git history were probably not that useful, as long as you're not running e.g. 4 or 5 branches in parallel with crossing history. Branch off, make change, merge back main, PR, is fine.

eru on Oct 26, 2023 [–]

Most of the time most PRs are small and can be squashed into a single commit, and still produce useful history.

Sometimes it makes sense to have multiple commits. The next step up the complexity ladder is:

- one preparatory refactoring commit that does _not_ change behaviour

- one simple commit that changes behaviour

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact