chore(dev): dry-run release CI on push #1
Conversation
This file contains hidden or 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 removes the "Build Python package" step from the "Build CI" workflow in favor of reusing the build job in the release CI workflow. It builds off the changes in adafruit#135 by adding more triggers to the release CI. I also removed some steps in the Build CI workflow that would only make sense if experimenting with GitHub Actions.
Owner
Author
|
This proposal is pending upstream patch in adafruit#135. I will rebase and submit the proposal upstream when that git remote is ready. |
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.
This removes the "Build Python package" step from the "Build CI" workflow in favor of reusing the build job in the release CI workflow. It builds off the changes in adafruit#135 by adding more triggers to the release CI.
I also removed some steps in the Build CI workflow that would only make sense if experimenting with GitHub Actions.