Permissions 使用Gitlab显示问题但隐藏代码
我有一个自托管的gitlab存储库。我不想发布代码，但我想为我的beta测试人员使用很棒的票务系统 是否可以有一个可以创建/评论问题但无权查看源代码的配置文件？2021更新： 这些表格在过去几个月里似乎有了很大的发展，您可以在这里浏览：Permissions 使用Gitlab显示问题但隐藏代码,permissions,gitlab,Permissions,Gitlab,我有一个自托管的gitlab存储库。我不想发布代码，但我想为我的beta测试人员使用很棒的票务系统 是否可以有一个可以创建/评论问题但无权查看源代码的配置文件？2021更新： 这些表格在过去几个月里似乎有了很大的发展，您可以在这里浏览： 原职： 好吧，看来Guest就是你要找的（不知羞耻地从中偷来的）： 您还可以查看以下状态： 根据我们的经验，这几乎涵盖了所有情况，可以轻松适用于任何组织 来宾-无法访问代码 记者-阅读存储库 开发人员-读取/写入存储库 Master—对存储库的读/写+
原职： 好吧，看来
Guest- 来宾-无法访问代码
- 记者-阅读存储库
- 开发人员-读取/写入存储库
- Master—对存储库的读/写+部分管理功能
- 所有者-读取/写入存储库+完整的管理功能
请注意，由于他们发布了“保护您的代码”的文章，报告者角色有能力管理（即管理）问题和标签，因此该文章与表相矛盾（）表中清楚显示来宾具有代码的读取权限。您在回答中使用了错误的表。我只想代表来自搜索引擎的用户澄清一下-请查看答案中的链接以获取有关此（）的最新信息。在这种情况下，如果项目是私有的，则来宾用户无权访问代码，但可以访问问题。如果项目是公共的或内部的，来宾用户也可以看到代码。
| Action | Guest | Reporter | Developer | Master | Owner |
|---------------------------------------|---------|------------|-------------|----------|--------|
| Create new issue | ✓ [^1] | ✓ | ✓ | ✓ | ✓ |
| Create confidential issue | ✓ [^1] | ✓ | ✓ | ✓ | ✓ |
| View confidential issues | (✓) [^2] | ✓ | ✓ | ✓ | ✓ |
| Leave comments | ✓ [^1] | ✓ | ✓ | ✓ | ✓ |
| See a list of jobs | ✓ [^3] | ✓ | ✓ | ✓ | ✓ |
| See a job log | ✓ [^3] | ✓ | ✓ | ✓ | ✓ |
| Download and browse job artifacts | ✓ [^3] | ✓ | ✓ | ✓ | ✓ |
| View wiki pages | ✓ [^1] | ✓ | ✓ | ✓ | ✓ |
| Pull project code | [^1] | ✓ | ✓ | ✓ | ✓ |
| Download project | [^1] | ✓ | ✓ | ✓ | ✓ |
| Create code snippets | | ✓ | ✓ | ✓ | ✓ |
| Manage issue tracker | | ✓ | ✓ | ✓ | ✓ |
| Manage labels | | ✓ | ✓ | ✓ | ✓ |
| See a commit status | | ✓ | ✓ | ✓ | ✓ |
| See a container registry | | ✓ | ✓ | ✓ | ✓ |
| See environments | | ✓ | ✓ | ✓ | ✓ |
| Create new environments | | | ✓ | ✓ | ✓ |
| Use environment terminals | | | | ✓ | ✓ |
| Stop environments | | | ✓ | ✓ | ✓ |
| See a list of merge requests | | ✓ | ✓ | ✓ | ✓ |
| Manage/Accept merge requests | | | ✓ | ✓ | ✓ |
| 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 | | | ✓ | ✓ | ✓ |
| Cancel and retry jobs | | | ✓ | ✓ | ✓ |
| Create or update commit status | | | ✓ | ✓ | ✓ |
| Update a container registry | | | ✓ | ✓ | ✓ |
| Remove a container registry image | | | ✓ | ✓ | ✓ |
| Create new milestones | | | | ✓ | ✓ |
| Add new team members | | | | ✓ | ✓ |
| Push to protected branches | | | | ✓ | ✓ |
| Enable/disable branch protection | | | | ✓ | ✓ |
| Turn on/off protected branch push for devs| | | | ✓ | ✓ |
| Enable/disable tag protections | | | | ✓ | ✓ |
| Rewrite/remove Git tags | | | | ✓ | ✓ |
| Edit project | | | | ✓ | ✓ |
| Add deploy keys to project | | | | ✓ | ✓ |
| Configure project hooks | | | | ✓ | ✓ |
| Manage runners | | | | ✓ | ✓ |
| Manage job triggers | | | | ✓ | ✓ |
| Manage variables | | | | ✓ | ✓ |
| Manage pages | | | | ✓ | ✓ |
| Manage pages domains and certificates | | | | ✓ | ✓ |
| Switch visibility level | | | | | ✓ |
| Transfer project to another namespace | | | | | ✓ |
| Remove project | | | | | ✓ |
| Force push to protected branches [^4] | | | | | |
| Remove protected branches [^4] | | | | | |
| Remove pages | | | | | ✓ |
[^1]: If **Allow guest to access builds** is enabled in CI settings
[^2]: Not allowed for Guest, Reporter, Developer, Master, or Owner