Allow the CI build to be run manually using the GitHub interface #590
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
Signed-off-by: James Couball <[email protected]>
jcouball
force-pushed
the
allow_manual_ci_build
branch
3 times, most recently
from
3508e56 to
3a9619c
Compare
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.
Signed-off-by: James Couball [email protected]
Your checklist for this pull request
🚨Please review the guidelines for contributing to this repository.
Description
It would be nice to be able to run the
masterbranch build to see if it is still working even though gem dependencies or latest OS versions were updated.With this change, the build can be triggered from the CI workflow on the GitHub actions page for this repository