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

1 messages from 2012-02-26 to 2012-02-26. Participants: Sitaram Chamarty.
Thread: https://gitlist.dev/t/29746

## Sitaram Chamarty, 2012-02-26 15:50

Subject: [gitolite] denying access by factors other than ref/path names
Message-ID: <20120226155041.GA28032@sita-lt.atc.tcs.com>
URL: https://gitlist.dev/e/20120226155041.GA28032%40sita-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


```