Add payu-version field to configs/ci.json schema
#35
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… required `payu-version` field
This was referenced Aug 21, 2024
jo-basevi
previously approved these changes
Aug 22, 2024
Co-authored-by: jo-basevi <johanna.basevi@anu.edu.au>
CodeGat
deleted the
model-config-tests-37-configs-ci-payu-version-field
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add a
payu-versionfield to the*-configsreposconfig/ci.jsonschema.Diffs are always funny with these schema updates, so run
diff au.org.access-nri/model/configuration/ci/1-0-0.json au.org.access-nri/model/configuration/ci/2-0-0.json.In this PR:
au.org.access-nri/model/configuration/cito2-0-0payu-versionfield to all levels of configurationReferences ACCESS-NRI/model-config-tests#37