Once I fix a bug, then I find another one.
Every day at my job.
At least once a day.
I commit each time I finish a block of work so about every 5 to 10 minutes. Then I share.
Here’s a rule I’ve stuck to for about a decade: if my laptop dies, I should only lose one day of work at most.
When I hit major milestones like writing all my tests or getting them all to pass, I will add, commit, and push. The whole point of version control is to have steps of working code to revert back if something goes wrong. It helps keep things organized.
Sharing changes gives me a little boost of happiness, especially since it’s linked to auto-deploying for me. So I share every one to three commits.
Plus, there’s really no downside.
For me, it’s commit then share right away!
I commit each time I get successful results.
Whenever I finish a specific update.
After every coding session to avoid losing my work.
Whenever I need CI to run or want someone to check my code. So like 20 times a day.
You don’t have a routine before you commit
I usually share at the end of the day.
I share whenever I make a commit.
Every time I make a change that I’m comfortable with. That’s pretty much every commit or a bunch of commits if I’m organizing changes by file or related code.
Not every commit, but I do when the changes are significant. Better safe than sorry.
Every time I commit, I share.
By the end of the day or after major changes.
Whenever I need CI to run. Usually, when I’m making a pull request.