Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
Oceas9769yiteratively at any stopping point. new branch for any feature and a lot of little comits hourly that way I can trace my code more granularly. also makes reverts easier with more points to go to
-
@gustash depends on the feature. if you are building small objects (SINGLE RESPONSIBILITY!) then you shouldn't need to save / commit much... save-commit, push, test, and move on.
-
doing huge commits (in my opinion) hides what you actually did. I like seeing commits/pushes like a punch card.
-
Commit when something has changed. New test written. New endpoint written. Class refactored. Something nice and small and self contained.
-
Anytime I accomplish something. I commit. It could be several times a day. Or several times within a ticket.
-
I think I do a minimum of around 60 "micro-commits" on a slow day.
It's easier to revert a single block of code for a small feature than to revert the whole day then add back in whatever you still need. -
commit on every task or related group of tasks/feature at branch level
multiple trunk merges along the day
Related Rants
When do you guys commit? Genuinely curious. I usually commit at the end of the day detailing all I did. What about you?
undefined
version control
commit
git