News for hackers. Stuff that matters.
Re:Git's commit workflow is backwards, and encourages bad ha... by thegigaraptor on Monday March 29, 2021 @11:08AM (#26622863)
> 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.

Re:Git's commit workflow is backwards, and encourages bad ha... by archi42 on Monday March 29, 2021 @11:27AM (#26623179)
This 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.
Re:Git's commit workflow is backwards, and encourages bad ha... by grayclhn on Monday March 29, 2021 @11:24AM (#26623109)
Hell, you could write it down in a separate text file if it’s really that big of a painpoint.
Re:Git's commit workflow is backwards, and encourages bad ha... by rorytbyrne on Monday March 29, 2021 @05:14PM (#26628253)
At that point I think the case for a tool like git-plan is pretty strong.
Re:Git's commit workflow is backwards, and encourages bad ha... by grayclhn on Tuesday March 30, 2021 @12:19AM (#26631224)
I think most teams use a bug tracker for this sort of thing, tbh.