Hmm, I'm afraid that the granularity you require is beyond what you can do
with a single git user. At our place, we haven't got a need to control
this: either you can write to the git repository or you cannot.
A compromise is in addition to allow write-access via SSH, you expose the
repositories for anonymous viewing over the git protocol, or HTTP.
If the above doesn't suit you, you have to have a look at Gitblit, or some
other repository manager that offers finer access control, or start
fiddling with the unix user/group, and have each developer use a different
ssh account in his git-urls ( git clone ssh://user1@server/repository and
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To view this discussion on the web visit
To post to this group, send email to email@example.com.
To unsubscribe from this group, send email to
For more options, visit this group at