From eb64781e0a1b5112cc208f8b7780b6525f6a69dd Mon Sep 17 00:00:00 2001
From: Sven-Hendrik Haase <svenstaro@gmail.com>
Date: Sat, 15 Aug 2020 18:30:12 +0200
Subject: [PATCH] Remove kvm/virtualbox capabilities
We've stopped providing kvm and virtualbox special devices as they are not actually necessary.
---
.gitlab/issue_templates/New Official Project.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/.gitlab/issue_templates/New Official Project.md b/.gitlab/issue_templates/New Official Project.md
index 26a1d62da..6772c6ae4 100644
--- a/.gitlab/issue_templates/New Official Project.md
+++ b/.gitlab/issue_templates/New Official Project.md
@@ -25,8 +25,8 @@ If you want to add a new official project, here are some guidelines to follow:
1. [ ] If the 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.
-1. [ ] If a secure runner is used, make sure the project's `.gitlab-ci.yml` specifies one of
- `tags: secure-general`, `tags: secure-virtualbox`, `tags: secure-kvm` depending on required capabilities.
+1. [ ] If a secure runner is used, make sure the project's `.gitlab-ci.yml` specifies
+ `tags: secure`.
1. [ ] Make sure that the *Push Rules* in https://gitlab.archlinux.org/archlinux/arch-boxes/-/settings/repository
reflect these values:
- `Committer restriction`: `on`
--
GitLab