8
gustash
9y

When do you guys commit? Genuinely curious. I usually commit at the end of the day detailing all I did. What about you?

Comments
  • 2
    every time I save I do a commit
  • 6
    iteratively 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
  • 1
    @mattwebdev damn, how many does that amount to a day?
  • 3
    @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.
  • 6
    doing huge commits (in my opinion) hides what you actually did. I like seeing commits/pushes like a punch card.
  • 6
    If she's the one then you commit tight away.
  • 5
    Commit when something has changed. New test written. New endpoint written. Class refactored. Something nice and small and self contained.
  • 3
    Thanks guys. Guess I need to form a new habit 😀
  • 1
    Anytime I accomplish something. I commit. It could be several times a day. Or several times within a ticket.
  • 1
    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.
  • 1
    commit on every task or related group of tasks/feature at branch level
    multiple trunk merges along the day
Add Comment