Welcome to the Kiln Knowledge Exchange

Question

1

Hey guys

I'd like to restrict new members from committing to our 'main' branch so that senior team members must review their code before it goes live (the senior team member would be responsible for the merge/commit).

What is the best way to achieve this in kiln?

Thanks! Trev

flag	asked Mar 1 2011 at 23:13 Trev 11●1

1

When you say "branch", do you mean named branches or branch repositories? – Tyler Hicks-Wright♦ Mar 2 2011 at 0:14

Tyler Hicks-Wright · Answer 1 · 2011-03-02 00:15:18Z UTC

If you mean branch repositories, what you can do is set their permissions on the project to be read-only (in the project settings page). Then, for the repositories you want them to be able to write to, you just override the project permissions and give them write perms (on the repo settings page).

Trev · Answer 2 · 2011-03-02 19:51:42Z UTC

0

Hey Tyler

Unforunately we are using named branches instead.

answered Mar 2 2011 at 19:51

Trev
11●1

Trev, the ACL extension to Mercurial would allow this, but it isn't yet supported by Kiln. I've put in a feature request for this support already: kiln.stackexchange.com/questions/3140/…. If you think that would help your situation, up vote that question to help the Kiln team prioritize it as a feature. – Chris Phillips Mar 2 2011 at 21:52

Branch Permissions

2 Answers