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

[gitolite] denying access by factors other than ref/path names

From
Sitaram Chamarty <sitaramc@gmail.com>
Date
Feb 26, 2012, 15:50 UTC
Message-ID
<20120226155041.GA28032@sita-lt.atc.tcs.com>

Gitolite now allows you to deny access using data other than ref names or path names.

For example, you can deny a push if:
  * it adds more then N new files (or variations, like changed
    files, binary files, new binary files...)
  * it contains autogenerated files that can't be caught by
    gitignore
  * it fails a "no non-merge first-parents" rule
  * you don't like the phase of the moon :)

Since the actual decision is done by a script you write, you can enforce pretty much any site-specific stupi^Wstandards, (like ensuring that junior developers push only their own commits).

http://sitaramc.github.com/gitolite/vref.html has all the gory details for anyone interested, and contrib/VREF in the latest pu branch has example code.

-- 
Sitaram
Message 1 of 1 in “[gitolite] denying access by factors other than ref/path names”
  1. Sitaram ChamartyFeb 26, 2012

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.