4 ms·
> Git forces you to write your commit message at the end of your coding session You could create a commit and —amend work into it if that is the route you’d li
by thegigaraptor 6y ago
> Git forces you to write your commit message at the end of your coding session
You could create a commit and —amend work into it if that is the route you’d like to take.
- grayclhn 6y agoHell, you could write it down in a separate text file if it’s really that big of a painpoint.
- rorytbyrne 6y agoAt that point I think the case for a tool like git-plan is pretty strong.
- grayclhn 6y agoI think most teams use a bug tracker for this sort of thing, tbh.
- archi42 6y agoThis in combination with a `git diff` in a split shell works very well for me. For adding changes, I often use `git add -p` - this also gives a nice opportunity to think about a change again. As a bonus, if I did not yet push, I can extend the commit (using --amend) or roll back to it when doing experimental changes. There is also the option to `git stash` some work away.