权限列表如下:
Action | Guest | Reporter | Developer | Master | Owner |
---|
Create new issue | ✓ | ✓ | ✓ | ✓ | ✓ |
Leave comments | ✓ | ✓ | ✓ | ✓ | ✓ |
Pull project code | | ✓ | ✓ | ✓ | ✓ |
Download project | | ✓ | ✓ | ✓ | ✓ |
Create code snippets | | ✓ | ✓ | ✓ | ✓ |
Create new merge request | | | ✓ | ✓ | ✓ |
Create new branches | | | ✓ | ✓ | ✓ |
Push to non-protected branches | | | ✓ | ✓ | ✓ |
Force push to non-protected branches | | | ✓ | ✓ | ✓ |
Remove non-protected branches | | | ✓ | ✓ | ✓ |
Add tags | | | ✓ | ✓ | ✓ |
Write a wiki | | | ✓ | ✓ | ✓ |
Manage issue tracker | | | ✓ | ✓ | ✓ |
Manage labels | | | ✓ | ✓ | ✓ |
Create new milestones | | | | ✓ | ✓ |
Add new team members | | | | ✓ | ✓ |
Push to protected branches | | | | ✓ | ✓ |
Enable/disable branch protection | | | | ✓ | ✓ |
Rewrite/remove git tags | | | | ✓ | ✓ |
Edit project | | | | ✓ | ✓ |
Add deploy keys to project | | | | ✓ | ✓ |
Configure project hooks | | | | ✓ | ✓ |
Switch visibility level | | | | | ✓ |
Transfer project to another namespace | | | | | ✓ |
Remove project | | | | | ✓ |
Force push to protected branches | | | | | |
Remove protected branches | | | | |
这是从gitLab的帮助文档上看到的,但是从实际的使用来看,将仓库设置为public时,对未受保护的develop分支,guest用户也是可以克隆的。
对于master分支,它默认是受保护的,所以developer角色对于master无push权限的,要想它有权限必须将master去保护。
参考链接
本文内容由网友自发贡献,版权归原作者所有,本站不承担相应法律责任。如您发现有涉嫌抄袭侵权的内容,请联系:hwhale#tublm.com(使用前将#替换为@)