Content
@
https://warpcast.com/~/channel/thomas
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
0 recast
21 reactions
Kiryoko
@kiryoko
Even if you're working alone, it's good to follow best practice. You can follow the GitHub workflow. and use a new branch for each feature. Then you open a pull request and merge it when it's done. Makes things really easier to manage especially if you use git worktrees. But as a rule of thumb, try not to go to the extremes (i.e. too many or too few commits) and don't commit "WIP" unfinished code to your master branch. That's what the workflow described above is for. Also, try to put gkod commit messages. Remember: the main purpose of git is version control. Thus, if you fuck something up, it's way easier to rollback changes. Good luck and keep BUIDLing!
0 reply
0 recast
0 reaction