Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See SciTools/.github#41 for the detailed context. Will need calling workflows on each of our repos.
Do we still believe in the workflows repository?
I personally have experienced a lot of frustrations of having one workflow that affects all repositories, as it gets in the way of me introducing a new concept (e.g. #28), means mistakes have large impacts (e.g. #88 vs #93), and makes it difficult to test things (e.g #108).
Templating is an alternative way of achieving the same thing, without the above problems. HOWEVER: we have agreed among the core devs that templating needs to be demonstrated to work BEFORE we apply it to workflows. In the meantime I felt it was important to embrace our current way of working.
Dependent PRs
ci-template-check.yml
tephi#206Plan to merge and test this before raising PRs on all the other repos
ci-template-check.yml
iris#6377ci-template-check.yml
iris-grib#628ci-template-check.yml
python-stratify#330ci-template-check.yml
iris-esmf-regrid#484ci-template-check.yml
cf-units#574ci-template-check.yml
nc-time-axis#344ci-template-check.yml
test-iris-imagehash#125ci-template-check-pr.yml
#117