4 ms·
> Commit and push often. Put a novel explaining yourself in the PR. And that's enough IMO. Someone reading the git changelog 5 years down the line most likely
by caskstrength 3y ago
> Commit and push often. Put a novel explaining yourself in the PR. And that's enough IMO.
Someone reading the git changelog 5 years down the line most likely wouldn't be able to find your "novel" in the PR and definitely won't appreciate if instead of a "novel" you ended up with a "short call" with the assigned reviewer explained what you actually did in your 50 "wip" commits.
- moron4hire 3y agoSomeone reading 5 year old git logs is lost to begin with.
- caskstrength 3y agoWhen debugging I routinely explore git blame and read the changelog. This sometimes leads to 3, 5 or even 10 years old code. Doesn't mean I'm lost.