Add separate workflow to manually trigger the CI tests on master #148
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
ryanmrichard
approved these changes
Jun 9, 2025
jwaldrop107
approved these changes
Jun 9, 2025
Member
|
🚀 [bumpr] Bumped! |
1 task
Contributor
Author
|
A secondary goal of this PR was to test if the changes in NWXCMake#51 work. The first manual trigger of the tests here that will confirm the NWXCMake changes success can be seen here: https://github.com/NWChemEx/ParallelZone/actions/runs/15541059768 |
Contributor
Author
The test succeeded! |
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.
Is this pull request associated with an issue(s)?
No.
Description
This PR adds a separate workflow that allows the CI tests to be manually triggered on the
masterbranch at any time. Whileworkflow_dispatch:could be added to the existing.github/workflows/pull_request.yamlworkflow, that would also trigger unnecessary extra license header addition checks, formatting runs, and documentation builds. This separate action does not perform those extra actions (although some of those may be useful to manually trigger separately in the future).TODOs
None.