Creating a Central Git Repository
In my previous post I discussed the steps necessary to create a Git repository. As it turns out, today I found the other piece of information that I was missing. That is, that when you create a central repository it must be bare. If you really want to share code (collaborate with others) in a repository, your "master" or central repository should be an empty one. That means that the only thing that it should contain is the repository but no source files (or any other files under version control). If you will recall, I ran into some hair-pulling problems because I couldn't push to the master repository. That was because the master branch had a working directory that had the master branch checked out. As a result, Git refused to push changes made in the slave to the master. By creating a bare repository you are insuring that this repository will not be worked on directly (i.e. it does not have a working directory)....