I spend much time splitting them up inside visual studio by file and individual lines changed to try and separate my many simultaneous changes into several somewhat usable commits. If I was stupid enough to make some big refactor at the same time I might just have to throw in the towel… It’s really painful after a few weeks to try and pick up the pieces of what I was doing but never commited too lol.
Comment on Manager: This task only takes 30 minutes. Why did it take you the whole day?
AVincentInSpace@pawb.social 11 months ago
Every time I commit I have to look through git diff
, figure out what the hell I actually did, come up with something intelligent to say about jt, possibly split the commit into multiple commits if I changed multiple things, do some shuffling with git reset
and git add
…
For some reason all my personal projects are all like 4K SLoC with 20 total commits, all of which include apologies for not doing more smaller commits
PixxlMan@lemmy.world 11 months ago
PoolloverNathan@programming.dev 11 months ago
^psst,^ ^git^ ^add^ ^-p^
etchinghillside@reddthat.com 11 months ago
Remind me what -p does.
PoolloverNathan@programming.dev 11 months ago
Patch add - it shows you particular changes you made, and you choose whether or not to include them in the commit. (You can then use
git stash -k
to stash only the changes you did not add, so you can test before you commit.)