yeah I pretty much do the same thing...if I go home without committing I feel dirty and disorganized. Also I try not to start coding a new feature without updating and merging.
I commit when two conditions are met:
1- Whole solution can be built without errors coming from my code (I'm not reponsible for others!).
2- I've written a reasonable amount of code that I'm sure won't be changed too much in the next commits.
6 comments so far
I try and commit before I shutdown and go home...assuming I won't break the build. Sometimes more and sometimes less.
2 years, 1 month ago by eriklane
At least daily, sometimes more - usually after I complete a feature and am ready to move on to something else.
2 years, 1 month ago by danhounshell
yeah I pretty much do the same thing...if I go home without committing I feel dirty and disorganized. Also I try not to start coding a new feature without updating and merging.
2 years, 1 month ago by hkarthik
I commit just about every time I do a refactoring, or have code to add that is thoroughly tested
2 years, 1 month ago by benfulton
I commit when two conditions are met: 1- Whole solution can be built without errors coming from my code (I'm not reponsible for others!). 2- I've written a reasonable amount of code that I'm sure won't be changed too much in the next commits.
2 years, 1 month ago by keyvan
I try and keep my commits to specific tasks. This may mean a few days without a commit depending on how big the task is.
2 years, 1 month ago by pauldy