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
-
No. Atomic commits.
One commit should contain a very small feature. That way it's easy to identify and revoke a feature.
Mine are usually a few hours apart. -
neofetch8067yI'm still new to git, but I try to commit for every change I make. I find it easier to track on what I did wrong at a later date.
-
each piece/feature that works, as soon as it works and can be commited as a logical whole.
the more often you commit, the less merge trouble you get. -
wizzzard8057yI instantly commit whenever my commit-alarm rings, no matter what I'm doing. This sometimes causes me to submit unfini
-
usually when it works, but if I have other obligations after work I'll move it to a branch prefixed with "WIP-" for "work in progress"; we have CI configured not to run on such branches.
-
When I've had progress where I'd like to keep its state, but not commit to keeping it as such, STASH!
When it works and I'm comfortable with how it's working and ready to move to another experimental upgrade, COMMIT!
When something isn't working and it's a recent action, BLAME ANOTHER DEV!
... I'm the only dev on my team... EVERYTHING IS OK!
Related Rants
Do you guys commit after your code works or when the day is over?
rant
git
commit
habits