how often do you author a new commit?do you make a bunch and then push them all at once?
when I finished somethingwhen I go to the toiletwhen I go to bed
every change is one commit
i dont use git
>>107868661One logical whole is one commit.I confess: If I've been lazy, I gather several days of work to make commits of to even it out.
>>107868661i commit feature to feature, if the intermediate status doesn't work then i don't commit
>>107868661On personal projects it's pretty much just whatever I feel like doing. I mostly just push to master unless I have something I specifically want to see the diffs of in github's PR viewer. For commits specifically i try to remember to keep commits focused but I very often get side tracked while working on features so my changes end up encompassing multiple files and it's hard to entangle that into multiple commits, so I just do one big commitProfessionally it's definitely way more disciplined, but that's because in a professional capacity you're often working on feature branches that are there for specific issues. Although this probably depends on where you work and how much git discipline is enforced
>>107868661ideally one ticket = one commit. so either a full feature or a bug fix. I don't commit unfinished work.that is for my PR. before I make a PR I use temp commits sometimes.
At the end of the day once for sure. When I finished something that I don't want to lose too.
>>107868661when my manager suspects I am withholding the code so that everything goes to hell when I leave
