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.
Splits our single workflow into two. This means that we can use
on: pull_request, which works much better™️ with other actions (like checkout).It also means (I think) that PRs which themselves modify the workflow(s), should be exercised in the PR (unconfirmed, but I think it should work like that), which grant has been running into a few times recently...
The rationale for
on: pull_request_targetwas that the github token given toon: pull_requestdoes not have enough permissions to read repo secrets and things, so it could not deploy. This is not so withpull_request_target.By splitting deploy into
on: workflow, the token its natively given has the appropriate permissions.The image from the
buildjob is shared with thetestjob in the same workflow as an artifact. It is not shared directly (e.g. as an artifact) with thedeployworkflow, but the build steps use a shared cache (seecache_fromandcache_to), which achieves basically the same result.