Content
@
0 reply
0 recast
0 reaction
Thomas
@aviationdoctor.eth
How often am I supposed to commit and push to GitHub? I work mostly on solo projects, so I treat my repo mostly as a backup feature, i.e., I might commit once at the end of each day, and even then in the least descriptive manner (“fixed some stuff”). Should I be pushing every time I make one discrete update, which might be several times a day? I feel that this may be one of those late realizations in life like when you accidentally find out you haven’t been flossing and brushing your teeth in the correct order
8 replies
2 recasts
56 reactions
Darryl Yeo 🛠️
@darrylyeo
Lots of benefits to committing atomically and as often as possible – easier to migrate features to other branches by cherry-picking or rebasing, easier to rollback or revert specific features out of order, easier to track down where a bug might have been introduced. More work upfront but well worth it in my opinion.
2 replies
0 recast
16 reactions
Thomas
@aviationdoctor.eth
That makes sense. I need to make it a habit because right now it’s more of an afterthought at the end of a coding session. Do you use the CLI or GitHub desktop?
2 replies
0 recast
3 reactions
Phil Cockfield
@pjc
Github Desktop, I find, is a pretty nice thin UI layer over git, without obscuring (to much) the mental model of the git concepts.
1 reply
0 recast
2 reactions
Thomas
@aviationdoctor.eth
I use it and definitely prefer it over CLI to visualize the changes in particular
0 reply
0 recast
2 reactions
