ci: dispatch clas12-validation
workflow runs
#126
Merged
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 workflow to dispatch
clas12-validation
workflow runs.Since this is a PR from a fork, the PAT is not accessible and the dispatch job will fail until this PR is merged.
To see an example working dispatch, see this equivalent PR against my fork, along with a successful workflow dispatch run; follow the "Workflow URL" link in the run's summary table to see the dispatched
clas12-validation
run.Unfortunately, a PR from a fork will never* have a successful validation dispatch, because of the inaccessible PAT; one possible workaround is having a contributor from a fork open a test PR on
clas12-validation
, manually changing the defaultcoatjava
fork and branch here, but that's not ideal.*well.. unless we use the dangerous
pull_request_target
trigger, which might be okay as long as we require approvals for running workflows for PRs from forks. IIRC the only secret we have is the PAT forclas12-validation
dispatches, but if we enablepull_request_target
, we need to be very careful if we forget about this and add another secret, especially if such a secret grants write access somewhere.