Azure DevOps 默认权限 [英] Azure DevOps default permissions

问题描述

在 Azure DevOps 中，git repos 的分支安全性将所有 Azure DevOps 组的强制推送"属性默认为未设置".这实际上拒绝了此权限.

我们在我工作的地方关注 gitflow，通常会明确拒绝持久分支、Master 和 Develop 的此权限；但是，对于功能分支，我宁愿将其默认为允许"，这样管理员就不必参与其中.有没有办法将所有分支的 Azure DevOps贡献者"组的强制推送"默认为允许"，除非明确设置为拒绝"?

干杯.

解决方案

你需要先了解Azure Repos的Securities

有两个级别的证券

1. 回购级别
2. 分支级别(默认情况下 - 从回购级别继承) - 您也可以更改此设置

默认，在 Azure Repos (Git) 中，重写和销毁历史记录(强制推送)在 Repo Level 是 Not Set.>

这是您创建的每个新分支的继承(默认).因此，对于在该 Repo 中创建的每个新分支，您的值都为 Not set.

您的要求不会直接实施，因为分支机构的所有证券默认都是从回购级别继承的.

你的问题的答案

1. 在存储库级别设置强制推送 - > 允许
2. 这将默认继承到您的存储库下的所有分支.
3. 到目前为止(您需要管理/保护)将这个设置更改为 拒绝 主，开发，质量检查

请注意此权限，因为您将其设置为允许在回购级别非常危险

In Azure DevOps, branch security for git repos defaults the 'Force push' property to 'Not set' for all Azure DevOps Groups. This effectively denies this permission.

We're following gitflow where I work and would generally deny this permission explicitly for persistent branches, Master and Develop; however, for feature branches I would rather this default to 'Allow', so that an admin doesn't have to be involved. Is there a way to default 'Force push' to 'Allow' for the Azure DevOps 'contributor' group for all branches, unless explicitly set to 'Deny'?

Cheers.

解决方案

You need to understand the Securities of Azure Repos first

There are two level of securities

1. Repo Level
2. Branch Level (By Default -Inherited from Repo Level) - YOU CAN CHANGE THIS ALSO

Default, in Azure Repos (Git), Rewrite and destroy history (force push) is Not Set at Repo Level.

This is the Inherited(by default) for every new branch you create. So you will have the value as Not set for every new branch you create with-in that Repo.

Your requirement will not be implemented directly since all the securities for a branch are by default inherited from the repo level.

The answer for your question

1. At repo level Set the Force Push - > Allow
2. This will be default inherited to all branches under your repo.
3. Change this Setting to Deny for the master, Develop, QA so far (which you need to administrate/secure)

BE CAREFUL ON THIS PERMISSION SINCE YOU ARE SETTING THIS TO ALLOW AT REPO LEVEL IS VERY DANGEROUS

这篇关于Azure DevOps 默认权限的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！