4 ms·
i don't know how people can build something and leave behind a coherent series of commits that tell a nice story of progressively building a thing. my commits
by parpfish 1y ago
i don't know how people can build something and leave behind a coherent series of commits that tell a nice story of progressively building a thing.
my commits include lots of false-starts that get abandoned and "i need to commit this interim state because i deprioritized this and will come back later".
the sequence of events that i used to build the thing isn't necessarily the best sequence of events to tell the story of what the final thing is.
sometimes you can get a good story by stacking PRs, but if the stack gets too deep you can end up with some rebase nightmares.
- Master_Odin 1y agoI'm a strong believer that PRs should be merged via a "squash and merge" strategy, with the singular commit being descriptive of the overall change and having a link back to the PR for deeper story analysis as needed. I'm also a staunch believer at this point that PRs should really focus on one thing as well. If when working on a bug you discover another semi-related bug? Open two PRs. Let main be the story of how code got from point A to B, and PRs be the story of how each incremental step was made.
- g-b-r 1y agoPRs only live on GitHub, what happens if it gets shut down or it accidentally loses some data?