Is there any sense in using git for a personal project of which I'm the sole dev? Just as a way to learn version control and such, or is it nothing like what it would be as a larger team?

I'd say definitely. I can't develop with source control these days. As long as you commit often, it allows you to roll back any mistakes easily, or branch off and try something without affecting your main development

What @linux-colonel said. Highly recommended, even for "throw-away" code.

Someone from devRant introduced me to http://gitlab.com, they have unlimited private repositories where no one can see your code :)

*unlimited free private repositories

There's tons of reasons to always use it. Many free providers of private repositories such as gitlab, bitbucket, etc.

It took me longer than I'd like to admit to discover Git, but now I use it at home even for mucking about with new stuff I'm trying to learn. Shure there is some stuff you might not learn being the sole dev, but it's a bit like asking "should I learn to drive even though I'll not be driving on the highway?"

for my system I'm the sole dev but use git for my CI. as I edit and save files they upload to my dev server, buy when I commit to my staging branch it will deploy to staging server, and when I merge staging into master it will auto push to all my production servers and also take my assets directory and auto push that to my CDN. I recommend people check out http://buddy.works for deployment and git management. has made my life way easier

OMFG a project without git, who would do that? 😨😨😨

Now being serious, yes it makes sense. Is a really good practice to naturally commit and keep versions of you code, be it a personal or team based project.

@itsmill3rtime is that not risky though? Modelling your branches after the your server seems like a bad idea to me (maybe it's ok as you're the only dev). I'd personally have a build pipeline - a single job that compiles/creates distributables, and various deploy jobs that pick up the artifacts from the previous build so the code goes SCM->DEV->TEST->RELEASE

@mohammed http://bitbucket.com offer the same too...

@linux-colonel at this time it's good. but if I do bring on additional devs they will make branches that merge into the existing ones and won't work directly on the existing ones if that makes sense. when it's just me it doesn't make sense to break it out too much

@itsmill3rtime I gotcha. My head just always goes to pipeline as soon as I hear CI lol

I always use git! Once you learn it it's soooo quick to use, never gets in the way of developing, and so many amazing pros!

Yes, you should use Git. You can learn a little bit more about branching, merging, rebasing, etc.

Also... Git for my solo projects has saved my ass when I go too deep down a rabbit hole and completely screw up my project... I just stash my changes to get it back to a working state.