ci: add manual trigger, update readme from code.json #16
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
wpbonelli
force-pushed
the
update-ci
branch
5 times, most recently
from
51b4407
to
fd8785d
Compare
jdhughes-usgs
approved these changes
Dec 21, 2022
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.
Since this repo only builds USGS programs and contains none of their source code, repo contents don't have a direct relationship to releases/version numbers, so the release mechanisms used for modflow6 and flopy aren't needed. Add
workflow_dispatchCI trigger to allow manually starting releases from the GitHub UI or CLI, e.g. from the project root:Also skip the step to publish a release if the workflow trigger is a
push— only run it on manual trigger. This allows merging changes tomasterwithout making a new release and likewise making a release without updatingmaster. With this PR, making a release just involves using the CLI or UI to manually trigger the workflow. If manually triggered, a release is automatically created, and a draft PR is opened into master to update theREADME.mdfromcode.jsonif the version table has changed. If triggered bypush, the workflow stops short of creating the release & PR.Here is a sample run from my fork. In this run a PR was not created since release versions in the table have not changed, but a release was created.
This PR also adds the markdown version of
code.json,code.md, as a release asset.