mrnil
I also found this particular annoying.
To build it from source, make sure to install all dependencies (check the provided Dockerfile for details), add both docker and docker/vendor to your GOPATH and then execute `bash hack/make.sh dynbinary`
I even use pu on my work machine to be able to test and use the latest features and never had a serious problem.
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/
> "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.
See man 7 gitcredentials on how to set it up.