> "git commit origin master"
That's not how to do it :)
> I wanted to make it so that they could also commit code into the same repo
No. Each developer works in her private repo, for sharing work you use a bare repo people push to / fetch from.
What do you mean by a "bare repo"? blhack wants to make it so that they commit code into the same repo. You could do that by setting up a repository somewhere, and then each person would clone it.
You could setup a remote and each person could clone that remote.
I left out the details about what you do after you clone (push/pull), but the point was that there is nothing special about the remote repository as far as it being "bare". Which turns out isn't right. You can set up a bare repository with no working directory as 2mur has pointed out. I wonder if that is a requirement. I always thought that if you clone a repository you can just start using it as a remote without additional hassle.
Sorry, you lost me; what's not right?
> You can set up a bare repository with no working directory
A bare repository has no working tree per se.
> I wonder if that is a requirement. I always thought that if you clone a repository you can just start using it as a remote without additional hassle
You can use bare and non-bare repositories as remote, but you should use only bare repositories (unless you know what you are doing). Here's a good explanation: http://bare-vs-nonbare.gitrecipes.de/