←back to thread

Beej's Guide to Git

(beej.us)
1062 points mixto | 1 comments | 05 Feb 25 00:07 UTC | HN request time: 0.207s | source
Show context
wodenokoto ◴[05 Feb 25 05:23 UTC] No.42944183[source]▶
On the promise of going back in time, I’m finding myself getting more utility of VS Codes timed snapshots than my own commits.

I find it hard to judge when things are in a good enough state to commit and especially good enough to have a title.

I might start writing a new function, decide that I want it to be a class only to give up the class and wanting to return to my almost complete function. Snapshot works pretty well for that, but got isn’t really centered around snapshots and doing good snapshots is not straightforward, at least to me.

What do you guys do?

replies(4): >>42944257 #>>42944328 #>>42947021 #>>42948158 #
1. shandor ◴[05 Feb 25 05:33 UTC] No.42944257[source]▶
A commit is literally a snapshot :) It is also very easy to make.

Stop worrying about titles and content and commit to your heart’s content.

When ready, restructure those snapshots into a coherent story you want to tell others by squashing commits and giving the remaining ones proper titles and commit messages. I use interactive rebase for that, but there are probably other ways too.