{"thread":{"id":"29746","subject":"[gitolite] denying access by factors other than ref/path names","startedAt":"2012-02-26T15:50:41Z","lastAt":"2012-02-26T15:50:41Z","messageCount":1,"participants":["Sitaram Chamarty"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"185461","messageId":"20120226155041.GA28032@sita-lt.atc.tcs.com","threadId":"29746","inReplyTo":null,"subject":"[gitolite] denying access by factors other than ref/path names","fromName":"Sitaram Chamarty","fromEmail":"sitaramc@gmail.com","sentAt":"2012-02-26T15:50:41Z","receivedAt":"2012-02-26T15:50:41Z","isPatch":false,"sender":{"key":"sitaramc@gmail.com","avatar":"https://avatars.githubusercontent.com/u/43316?v=4"},"body":"Gitolite now allows you to deny access using data other than ref\nnames or path names.\n\nFor example, you can deny a push if:\n\n  * it adds more then N new files (or variations, like changed\n    files, binary files, new binary files...)\n  * it contains autogenerated files that can't be caught by\n    gitignore\n  * it fails a \"no non-merge first-parents\" rule\n  * you don't like the phase of the moon :)\n\nSince the actual decision is done by a script you write, you can\nenforce pretty much any site-specific stupi^Wstandards, (like\nensuring that junior developers push only their own commits).\n\nhttp://sitaramc.github.com/gitolite/vref.html has all the gory\ndetails for anyone interested, and contrib/VREF in the latest pu\nbranch has example code.\n\n-- \nSitaram\n\n"}]}