I have a project with branch restrictions.
In the branch restriction at project level on branch develop some people have write access.
In a repo inside the project I need to remove the write access for Everyone. So I try to set in web UI "Only specific people or groups have write access" and do not set any person.
If I see the api call I can see this payload:
{
"values": [
{
"branch_type": "development",
"branch_match_kind": "branching_model",
"kind": "push",
"users": [],
"groups": []
},
{
"branch_type": "development",
"branch_match_kind": "branching_model",
"kind": "restrict_merges",
"users": [],
"groups": [
{
"slug": "devreviewers"
}
]
},
{
"branch_type": "development",
"branch_match_kind": "branching_model",
"kind": "delete"
},
{
"branch_type": "development",
"branch_match_kind": "branching_model",
"kind": "force"
}
]
}
The restriction of ind "push" is corected sended with void groups and users.
This setting don't have effect. Devreviewers still have write access to branch.
I tried also with a void group.
Inside Nobody there aren't any users.
The result is the same. Devusers can still push on develop branch.
Now I have to use an alternative solution. The unique I can image is move the repo in another project. But I cannot understend how Nobody could be less restrictive then someone.
Hi @[deleted]
I think this is documented here. It's overlapping the inherited permission, so it's applying both permissions: Devreviewers + NoBody or Devreviewers + [Nothing] = Devreviewers. It doesn't override or negate, it combines it.
Hi @[deleted],
This behavior is documented: overlapping permissions combine instead of overriding or negating each other.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.