Add post-release CI which triggers wheelhouse creation via gh #1102
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
This requires a PAT to be created and stored in the appropraite repository secret
mondus
reviewed
Aug 25, 2023
mondus
approved these changes
Aug 25, 2023
|
Manually triggerd the new post-release CI post merge: https://github.com/FLAMEGPU/FLAMEGPU2/actions/runs/5974872939 Which successfully triggered a run of the wheelhouse deployment ci: https://github.com/FLAMEGPU/FLAMEGPU2-wheelhouse/actions/runs/5974874888 So that's behaved as intended, and will auto rebuild the wheelhouse on the next github release |
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.
Adds a CI workflow which is triggered by release publication, which will then trigger a different workflow on another repository.
This required a PAT to be created and stored in the appropraite repository secret, and it will need renewing ~once a year.
We could extend this new workflow to also trigger docs builds for us (which fetches content from FLAMEGPU2's master branch when rebuilt).
Hosted at https://whl.flamegpu.com, with basic instructions. The next release will need the release notes adapting for this.
Closes #645