ci: allow custom actions runner to be defined #3989
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.
Fixes #0000
Companion of #3988
Changes proposed in this pull request:
Allow custom GitHub Actions runner to be defined in the reusable frontend & backend workflows. This allows third-party vendors to optionally pass a new input
runner_type
which specifies on which machine the jobs are being run (be it a custom GitHub-hosted runner or a self-hosted one).Hypothetical example of a calling workflow:
It's important to note that this new input is optional and will default to
ubuntu-latest
if not defined by the calling workflow.Reviewers should focus on:
Screenshot
QA
Necessity
Confirmed
composer test
).Required changes: