action #151675
Updated by amanzini 6 months ago
When I fork a JobGroup repo, it's required to setup APIKEY / APISECRET variables in order to let the CI run the checks. If I am an openQA admin, when I push to master on my fork, fork of a JobGroup repo, the CI/CD runs check and, when passed, deploys the result to OSD. This risks risk to propagate any error in the global environment and can be avoided by running the CI/CD for deployment only on one "source-of-truth" repository, with a protected master branch.