We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In a similar vein to https://github.com/ACCESS-NRI/access-om2-configs/blob/main/.github/workflows/generate-initial-checksums.yml, collaborate with @anton-seaice to create a similar user-dispatchable workflow for checksum creation.
Some initial questions (which may require a slight reworking of ACCESS-NRI/model-config-tests CI):
ACCESS-NRI/model-config-tests
The text was updated successfully, but these errors were encountered:
I think in a PR, compare against the checksum in the branch being merged into.
For a user-triggered workflow, maybe the user has to specify the branch with the checksum to compare to?
Although, typically, a branch named
feat-025_jra55do_ryf-iss191 could be compared to dev-025_jra55do_ryf
feat-025_jra55do_ryf-iss191
dev-025_jra55do_ryf
Anyway - I think I don't understand the question ... in generating initial checksums there is nothing to compare against ... ?
Sorry, something went wrong.
Ah correct, initial checksums wouldn't have to compare to anything :D I was thinking about the future case for PRs
Closed via #121
CodeGat
No branches or pull requests
In a similar vein to https://github.com/ACCESS-NRI/access-om2-configs/blob/main/.github/workflows/generate-initial-checksums.yml, collaborate with @anton-seaice to create a similar user-dispatchable workflow for checksum creation.
Some initial questions (which may require a slight reworking of
ACCESS-NRI/model-config-tests
CI):The text was updated successfully, but these errors were encountered: