Skip to content
Snippets Groups Projects
Verified Commit 567912d8 authored by Sven-Hendrik Haase's avatar Sven-Hendrik Haase
Browse files

Document more stuff for new GitLab projects

parent 6d05d9a7
No related branches found
No related tags found
No related merge requests found
Pipeline #488 passed
......@@ -12,3 +12,10 @@ the "Developer" role. The idea is to let these people mostly manage their own pr
4. If a project needs a secure runner to build trusted artifacts, coordinate with
the rest of the DevOps team and if found to be reasonable, assign a secure runner
to a protected branch of the project.
5. Make sure that the Push Rules in https://gitlab.archlinux.org/archlinux/arch-boxes/-/settings/repository
tick all of "Committer restriction", "Reject unsigned commits", "Do not allow
users to remove tags with git push", "Check whether author is a GitLab user",
"Prevent committing secrets to Git". All of these should be activated by
default as per group rules but it's good to check.
6. The Protected Branches in https://gitlab.archlinux.org/archlinux/arch-boxes/-/settings/repository
should specify "Allowed to merge" and "Allowed to push" as "Developers + Maintainers."
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment