git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Permissions and authorisations in git repository

From
KKKonstantin Khomoutov <flatworm@users.sourceforge.net>
Date
Jan 28, 2011, 12:06 UTC
Message-ID
<20110128150631.33be0a9d.kostix@domain007.com>
In-Reply-To
<1296214884133-5969556.post@n2.nabble.com>

On Fri, 28 Jan 2011 03:41:24 -0800 (PST) vikram2rhyme <vikram2rhyme@gmail.com> wrote:

> I am wondering if there are any permission and authorization control
> over git repository.
[...]

In the simplest case -- r/w access via SSH -- those who know the login/password or possess the necessary private key have (full) access to the repository. The repository can also be made accessible for read-only via Git protocol (as a whole as well). This can be used for simple write/read access discrimination. If a more fine-grained control is needed, third-party tools exist: gitolite: https://github.com/sitaramc/gitolite gitosis: http://swik.net/gitosis

Note that as Git does not suffer from a centralised VCS syndrome of having a single repository shared by everyone involved, the problem you're facing might not exist at all: every developer or a group of related developers maintains their own repository and a "central" repository (in whatever sense you're willing to put into it) is owned by a special person or a group of persons.

Previous: vikram2rhymeNext: Enrico Weigelt
Message 2 of 3 in “Permissions and authorisations in git repository”
  1. vikram2rhymeJan 28, 2011
  2. Konstantin KhomoutovJan 28, 2011
  3. Enrico WeigeltJan 29, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.