Right, so I was late but I am there now – in Github. I spent a few hours yesterday to setup everything and while it took a bit longer than with Subversion I still think it was easier than expected.
This post is for other Windows users who want a short overview of what you need to do to become a Githubber.
- Get an account at Github.
The reason we do this first is because Github have a really good guide for beginners.
- Download Git for Windows.
- Follow the guide at Github (read both “Set Up Git” and “Create A Repo”).
- You should now have submitted your first commit to your repo through the command line or the Git GUI. Congratulations!
- If you’re like me, you don’t like the cmd-way (I really tried to!) and want something visually appealing instead. I found the Git Extensions project which suited me well. Besides giving you a complete overview of the repo, it also integrates with VS2010 by adding a “Git” menu. Handy!
That’s actually all I had to do. The only problem I had was with Git Extensions because it used PuTTY for SSH while the guide used OpenSSH. To fix it I had to generate a new SSH key (public and private) in PuTTY and add the public key to my Github account. Apparently PuTTY is more suited for Windows than OpenSSH is.
Git tips for Visual Studio
Name the README file with the “.markdown” file extension and use VS extension “Markdown Mode” to edit it.
Create a new file called “.gitignore” in the root of the repository and fill it will directories/files that you don’t want to stay in the repository. Following is a .gitignore file which filters Visual Studio and ReSharper files:
bin obj *.suo *.user *.csproj.user *.cache *.resharper.user _ReSharper* *.sln.docstates*
After all, Git wasn’t as scary as I had believed and the Github website makes it a really nice experience with its beautiful UI and social features.