简体   繁体   English

Atlassian隐藏-分支级别权限

[英]Atlassian Stash - Branch level permission

We use Atlassian Stash. 我们使用Atlassian Stash。

I am admin of a Project. 我是一个项目的管理员。 There is a repository in the project. 项目中有一个存储库。 I do not give any permission to anyone for the repository in the 'Repository level'. 我不向任何人授予“存储库级别”中存储库的任何权限。

There are 2 branches in the repository. 存储库中有2个分支。 'master' and 'release/r30'. 'master'和'release / r30'。

I want my team members to commit their changes only in 'release/r30' branch. 我希望我的团队成员仅在“ release / r30”分支中提交他们的更改。

So, In the Branch level permission, I select ''release/r30' and give permissions to my team members. 因此,在“分支”级别权限中,我选择“ release / r30”并将权限授予我的团队成员。

But - Stash is throwing an error like this 'remote: You have insufficient permissions to update' 但是-Stash抛出类似“远程:您没有足够的权限进行更新”的错误

If i give the repository level permission write permission - it works fine. 如果我授予存储库级别的权限写权限-它可以正常工作。 but i do not want this. 但是我不想要这个。

Am i doing anything wrong here? 我在这里做错什么了吗?

Ex-Stash developer here. 前隐藏开发人员。 From the docs: 从文档:

https://confluence.atlassian.com/display/STASH/Using+branch+permissions https://confluence.atlassian.com/display/STASH/Using+branch+permissions

Branch permissions are used to limit branch access to specific people who must still have write access to the project or repository. 分支权限用于将分支访问限制为必须仍然对项目或存储库具有写访问权的特定人员。

Basically, the branch permissions work as a restriction over the normal repository write permission. 基本上,分支权限是对常规存储库写权限的限制。 Once you have write access you can restrict access via branch permissions. 拥有写访问权后,您可以通过分支权限来限制访问。

Any reason why you don't want to give your team write access? 您为什么不想让您的团队拥有写权限?

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM