禁止Gerrit推送至裁判/裁判/大师 [英] Gerrit push to refs/for/master prohibited

查看:94
本文介绍了禁止Gerrit推送至裁判/裁判/大师的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我昨天更新了 All Project 访问权限,人们说他们今天早上不能将更改推送到存储库.恢复访问权限后,他们仍然无法将更改推送到存储库,只有clone可以正常工作.在将更改推送到远程存储库时,它说:

I have updated the All Project access permission yesterday, people says that they cannot push changes to repository this morning. After I recovered the access permission, they still cannot push changes to repository, only clone works fine. While push changes to remote repository, it says that:

![remote rejected] HEAD -> refs/for/master (prohibited by Gerrit)

我们所有其他项目都是从所有项目的访问权限继承的,我将访问权限更新为最低级别(即 Anonymous 可以将分支推送到refs/heads/* )进行测试,但是我发现 Administrator 也无法将更改推送到存储库!

All our other projects are inherit from All project's access permission, I updated the access permission to the lowest level (i.e. Anonymous can push branch to refs/heads/*) for test, but I find that the Administrator cannot push changes to the repository too!

是否需要添加其他设置?

Is there any other settings need to add?

推荐答案

要推送到审阅分支(即refs/for/*),必须为引用refs/for/refs/*设置权限推送".然后,您还需要引用refs/heads/*的权限Label Code ReviewLabel verifiedSubmit来进行实际的代码审查.

To push to the review branches (i. e. refs/for/*), you have to set the permission "Push" for the reference refs/for/refs/*. You then also need the permission Label Code Review, Label verified and Submit for the reference refs/heads/* to do the actual code review.

如果您不想查看代码,而是直接推送到分支,则您的权限是正确的,但是您还必须推送到refs/heads/master,而不是refs/for/master.

If you don't want code review, but push directly to the branch, then your permissions are correct, but then you also have to push to refs/heads/master, and not refs/for/master.

这篇关于禁止Gerrit推送至裁判/裁判/大师的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆