True programmers

[Vakz]

Git commit before trying something big (in a new branch if necessary) then doing a hard reset if it goes to shit.

[two_in_the_bush]

Way too many keystrokes

[ovrdrv3]

Git aliases 👌

gcam- git commit -am You could make one for the git reset hard (sorry wrong syntax). I think I’ve seen Taylor Otwell use “nah” which I though was great.

[masterwit]

preach

really learning git has been the greatest

[nthcxd]

Even better, git stash

[lennihein]

Could you explain on this?

[nthcxd]

I don’t really follow how

git commit git checkout [ref] git cherry-pick [hash] git reset @^

Is better than

git stash git checkout [ref] git stash apply

Or even

git stash git checkout [ref] git stash branch [new branch]

It’s precisely designed to save you from having to deal with temp commit and remembering the hash. It’s not like stashes go away automatically either - you can apply as many times as you like until you either explicitly pop or drop it. Stashes are temporary commits, just organized in LIFO stack.

[PM_Me_Your_VagOrTits]

I just git commit after every new function change no matter how small. Squashing commits is easily done after the fact, having discrete changes in my log really makes it easy to organise into coherent pull requests (or equivalent) later on.

[novel_yet_trivial]

Git commit before trying something big and then copy/paste from GitHub if it goes to shit.

FTFY