When should I make the first commit to source control?

a thoughtful web.

commentspostsbadges

Good ideas and conversation. No ads, no tracking. Login or Take a Tour!

When should I make the first commit to source control? · 5

user-inactivated · 4525 days ago

arstechnica.com · #programming

tweet · htmlmarkup tips · 0

jmcs · 4524 days ago · link ·

I personally believe in committing as early as possible, it's never too soon to screw up your code and having to go back.

+discuss+discuss

–

temple · 4524 days ago · link ·

Same here, especially with something like git.

No one has to see my changes until I push them, and if I really care that I make too many local commits (I don't) could clean them up with git rebase.

+discuss+discuss

user-inactivated · 4523 days ago · link ·

I usually don't do an initial commit until I'm sure I'm not going to abandon what I'm working on. Then my first commit message is an outline of what I was thinking and where I expect to go with it. That way browsing through the history always eventually hits a high-level overview. People more conscientious about maintaining separate documentation than me are probably better off doing an initial commit earlier though.

+discuss+discuss

user-inactivated · 4524 days ago · link ·

  #!/usr/bin/env python
  import sys
  
  def main():
    sys.exit()
  
  if __name__ == "__main__":
    main()

:wq

git commit -m "initial commit"

+discuss+discuss

briandmyers · 4524 days ago · link ·

Seems like a no-brainer - as soon as you have anything you wouldn't want to lose (say, if your HD were to crash).