Repository permissions

Ever had the need to give someone permissions to triage merge request, but not give them commit access? Well, now you can, thanks to our new finer-grained repository access permissions.

This also means to can set some users as reviewers (and committers), while the rest of the committers won’t get notified about new merge requests. This is something some of the larger projects here on Gitorious with large groups of committers has requested.

6 Comments

  1. Posted November 29, 2009 at 3:39 am | Permalink

    While I’m sure that’ll be a useful feature for someone… I hope this was not the intended solution to KDE’s merge request problem. :/

    It doesn’t address the problem of individuals within a group needing different mail settings for the repositories the group is subscribed to. It also keeps all the power, responsibility and tedious maintenance strictly in the hands of administrators, instead of empowering users to set appropriate mail settings for themselves based on their own interests.

  2. Posted November 29, 2009 at 4:55 am | Permalink

    however… there does seem to be an rss feed for amarok’s merge requests. :)

    does that feed include all changes to merge requests? if not, can it? perhaps we could use rss instead of email… that would give everyone the freedom to receive all the information, and only the information, that they’re interested in. and the freedom to change their interests at any time. freedom is important to us. ;)

  3. Posted November 29, 2009 at 5:17 am | Permalink

    however… it’s still up to the *amarok* admin whether *I* receive amarok merge mail. unless I disable all gitorious mail entirely.

    so I really, really hope there’s never anything important in that gitorious mail, because apparently there are 93 unread messages there that I’m never going to check; they might all be amarok merge requests, they might not.
    oh well, it’s not like my qt merge request was going anywhere anyways :P

  4. Posted November 29, 2009 at 7:52 pm | Permalink

    Chani, separating the notion of committers from reviewers is step one towards a better way of notifying people of things that may be even more relevant to them.

  5. Posted November 29, 2009 at 8:16 pm | Permalink

    ohh, so there’s more coming? :) ok, I’ll try to stop freaking out and wait for you to implement it ;)

    but you are planning to give *users* control over this and not just admins, right?

  6. Jesse Greenwald
    Posted December 25, 2009 at 10:24 pm | Permalink

    How about branch level permissions? It would be nice if only a few people on a team could be given access to commit to “master”. For people without commit access to master on the team, they would be allowed to create their own branches for changes. The could then be reviewed and merged into master once they are approved. I realize this is nearly identical behaviour as cloning an entire repository and then submitting a merge request. However, I think that branch level permissions would be lighter weight and allow a team to more easily review everything that goes into the master branch.


Post a Comment

Required fields are marked *

*
*

Follow

Get every new post delivered to your Inbox.

Join 713 other followers

%d bloggers like this: