Commit b532d195 authored by Levente Polyak's avatar Levente Polyak 🚀 Committed by Jelle van der Waa
Browse files

issue templates: require to disable 'users can request access'

This shouldn't be possible as it may lead to accidentally allowing
external users to be added to a project.
We should only add members to a project or group on staff request to
devops.
parent beb548e3
Pipeline #7073 passed with stage
in 34 seconds
...@@ -39,6 +39,8 @@ If you want to add a new official project, here are some guidelines to follow: ...@@ -39,6 +39,8 @@ If you want to add a new official project, here are some guidelines to follow:
1. [ ] The *Protected Branches* in https://gitlab.archlinux.org/archlinux/my-example/-/settings/repository should specify 1. [ ] The *Protected Branches* in https://gitlab.archlinux.org/archlinux/my-example/-/settings/repository should specify
`Allowed to merge` and `Allowed to push` as `Developers + Maintainers.` `Allowed to merge` and `Allowed to push` as `Developers + Maintainers.`
1. [ ] Disable unneeded project features under *Visibility, project features, permissions* (https://gitlab.archlinux.org/archlinux/my-example/edit) 1. [ ] Disable unneeded project features under *Visibility, project features, permissions* (https://gitlab.archlinux.org/archlinux/my-example/edit)
Always:
- `Users can request access`: `off`
Often, but not always: Often, but not always:
- Repository -> Container registry - Repository -> Container registry
- Repository -> Git Large File Storage (LFS) - Repository -> Git Large File Storage (LFS)
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment