覆盖贡献者组权限 [英] Overriding the Contributor group permissions
问题描述
TeamA 拥有需要访问工作项的开发人员、质量检查人员和业务人员.他们被添加到贡献者组.但是，贡献者可以访问只有开发人员应该拥有的源代码.
TeamA has developers, QA and business people all of who need access to workitems. They get added to the Contributors group. However, Contributors has access to source code which only devs should have.
我们希望关闭贡献者对存储库分支的访问，以防止非开发人员访问源代码.
We want to turn off Contributor access to repository branches to keep non-devs out of source code.
我们创建了一个 DeveloperAccess 组，并赋予它与默认贡献者组相同的权限.然后我们将 Contribute 的 Contribute、Create branch、Create Tag 等权限设置为 Denied(此处'Not set' 不是一个有效选项)
We created a DeveloperAccess group and gave it the same permissions as the default Contributor group. We then set Contribute, Create branch, Create Tag etc permissions of Contribute to Denied ('Not set' is not a valid option here)
一旦我们这样做，DeveloperAccess 中的用户就不能再使用存储库.
As soon as we do, the users in DeveloperAccess can no longer use the repository.
然后我尝试关闭继承而不更改开发访问权限.
I then tried to turn off Inheritance with no change in dev access.
我希望如果 DeveloperAccess 具有参与、参与拉取请求、创建分支、创建标签、管理笔记和阅读的权限，那么该组中的任何用户都可以为分支做出贡献，无论其访问权限或成员身份如何默认的 TFS 贡献者组.
I would expect that if DeveloperAccess had permissions to Contribute, Contribute to pull requests, Create Branch, Create tag, Manage notes and Read then any user in that group would be able to contribute to the branch regardless of the access or membership of the default TFS Contributor group.
显然，我遗漏了一些东西.
Obviously, I'm missing something.
推荐答案
我相信我刚刚找到了答案.我没有尝试所有的继承组合.
I believe I just found the answer. I didn't try all combinations of the inheritance.
我关闭了继承，然后我能够将贡献者组中的权限设置为未设置".
I turned off inheritance and then I was able to set the permissions in the Contributor group to 'Not set'.
未设置"似乎是答案，现在我的 DeveloperAccess 组按预期控制对分支的访问.
'Not set' seems to be the answer, now my DeveloperAccess group controls access to the branch as expected.
贡献者不再显示在存储库的安全列表中.
And Contributor no longer shows in the Security listing for the repository.
这篇关于覆盖贡献者组权限的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
