From 14580102e97c9a3d22aa3aa1cd561be4bbdaf378 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Matthias=20B=C3=BCchse?= Date: Tue, 26 Nov 2024 21:42:45 +0100 Subject: [PATCH] Mention that a Github fork may be required in some cases MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Matthias Büchse --- standards/certification/pipeline.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/standards/certification/pipeline.md b/standards/certification/pipeline.md index b86670e489..c2e3aa5861 100644 --- a/standards/certification/pipeline.md +++ b/standards/certification/pipeline.md @@ -30,6 +30,10 @@ to be used for purposes other than compliance testing (such as the - `cd standards` - `git checkout -b feat/add_my_cloud` + **CAUTION**: If you are not a member of the SCS Github org, this won't work. + Ask the SCS team (or other members) to add you. Alternatively, you may fork the repository on + Github first and then clone the fork. + 3. Add your subject to the results table. This is necessary so your subject shows up in the [compliance monitor web-site](https://compliance.sovereignit.cloud/page/table). Add the following lines (substituting all-caps parts except `HM`):