43
hanuor
8y

Since you're here, let's make something very clear.
There are four kinds of people in this world:
1. Idiot fucks who commit everytime they write a single loc
2. Professional programmers who commit when they complete a module/functionality
3. Lost souls who commit to their girlfriends
4. People who don't use git.
Understand?

Comments
  • 16
    Commit early, commit often, squash when merging.
  • 2
    I work with some one who makes very few commits he pretty much completes a project and commits.
  • 4
    @CogInTheWheel Ikr! Some people like to showoff their 'commits' on github by committing everytime they accomplish writing a single line of code. *Facepalm*.
    In your case, that someone is truly a very sensible person.
  • 2
    @Artemix Ah! at least you're following the scrum methodology (which is tbh a very good practice).
  • 1
    @Artemix, and small commits on a big task is easier for your pairs or leads if you use code review with merge requests. I they don't have time enough to check the whole branch they can easily check commits by themselves between their own tasks.
  • 2
    I tend to commit at the end of each day. Never know if my laptop is going to burn down overnight.

    Plus when working with multiple developers it catches conflicts early.
  • 0
    Svn makes me cut myself
  • 0
    git commit -m "changed stuff"

    At the end of day and you forgot to commit and is too tired to sort the files out. Happens way more than I like to admit :|
  • 0
    I usually commit a fair bit, for every bugfix, feature or maintenance. I'll do it with commit emojis for clarity (https://github.com/dannyfritz/...). Then, later in the day (when I've finished a major feature/improvement/fix/whatever), I'll push all the commits, and my workflow is visible.
  • 1
    So basically "Or you Git it, or you don't"
  • 0
    Our team run SCRUM. We used to have a guy commit once per story. No matter how large is the story.
Add Comment