azure devops中文显示乱码,Azure DevOps默认权限

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

Repo Level

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

At repo level Set the Force Push - > Allow

This will be default inherited to all branches under your repo.

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

评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值