ACCESS-NRI / model-config-tests

Tests for checking model configurations
Apache License 2.0
0 stars 1 forks source link

Add Repro Checks to `dev-*` branches #38

Open CodeGat opened 2 months ago

CodeGat commented 2 months ago

Background

Since the QA checks are run before the Repro checks in release-* branches, we might as well add them to dev-* as well. This gives the dev-* PRs the ability to test reproducibility before opening a release-* PR and potentially having to go back and open a dev-* PR again if one gets an unfavourable reproducibility result.

Considerations

CodeGat commented 2 months ago

Just working on the dev-* branch repro checks and have bumped into a security hole. The GitHub Environmment that allows us to deploy to Gadi only allows deployment from protected (source) branches (release-, dev- ) This protects us from bad actors modifying the workflow files and opening an (auto-CI-running) PR because they must first get it into `dev-via a pull request (which currently doesn’t access the Gadi Environment). In order to allow Environments (and hence repro) on PRs intodev-*`, we have three options:

anton-seaice commented 2 months ago

There is a github setting "Fork pull request workflows from outside collaborators" which you can set to " Require approval for all outside collaborators " - I had assumed this would be sufficient ?

CodeGat commented 1 week ago

Yeah I'm starting to think the above security hole isn't as much of an issue. We lock down who has write access in our own org, and forks don't have access to upstream environments.