Branch permissions to limit write access to specific folders

Issue #15599 wontfix
Nikita Rukavkov
created an issue

Hello. Our reposotory has two root folders. Example:

  • Sources
  • Misc

Also we have two branches. Example:

  • develop
  • master

And two group:

  • master-commiters (can push to master and develop branch)
  • develop-commiters (can push to only develop branches)

I want to grant permission to Misc project for group develop-commiters into master branch. But I don't want to grant permissions to push to another folders in master branch.

It would be great if you will extend branch permission rules and add permissions to folders.


Comments (8)

  1. Alastair Wilkes staff
    • changed status to open

    Interesting suggestion! I don't think we've seen this before.

    Is there a reason that you don't split Sources and Misc into their own repositories? Seems like that would solve this problem.

  2. Nikita Rukavkov reporter

    Hello Alastair
    We had 4 repositories before and it was uncomfortably for us. We created mono repository.
    Case I described before it's just example. We have 4 folders in root repo now. And all of this folders contains another projects assigned to sub teams.

  3. Alastair Wilkes staff

    Hi Nikita,

    Thanks for the response. I think it's pretty unlikely we'll implement this, but I'll leave this open for a while in case we get feedback from other customers.

    In the meantime, are you familiar with submodules? I think they could be helpful for your use case.

    Bitbucket PM

  4. Alastair Wilkes staff

    Hi there,

    After review, I think it is unlikely that we will implement this in the next 6-12 months, so we are closing this issue. For the immediate future we are focused on improving the pull request user experience - and when we do work on improving branch permissions, there are other items (like being able to require specific approvers) that would be higher priority than this one. Of course, if there is more demand for this down the road we can reopen it, but for now I'm going to close this.


  5. Log in to comment