Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • I agree with the use of Git. I use it for projects, even if I'm the ONLY developer. Commented Dec 3, 2011 at 5:11
  • I'm starting to as well. I wouldn't with SVN...but with Git, it's so easy to create and manage a repo without even dealing with a server, that it's getting harder to justify not saying git init the second you start working on something. Commented Jun 8, 2013 at 0:42
  • without the right .gitignore a git repo is basically useless. That's the only thing that you have to have in place aside from git init Commented Sep 18, 2013 at 16:26
  • "but merging is a bit more problematic" - if OP only uses it himself, there's not gonna be a lot of merging, is there? Merging back his own feature branch into his own master maybe, but any code he receives from his boss would rather go in a new commit, no? I have no experience with SVN though, only git. Commented Feb 27, 2019 at 14:48
  • 2
    “There’s not gonna be a lot of merging” until there is. Any project, even if it’s a hobby project, will eventually require the dev team (which could be one person) to work on two things at once. Then you have to merge, and at some point you will encounter merge conflicts. Commented Mar 2, 2019 at 13:23