Use the docker image for the label check action to improve speed #351
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.
Description
Another follow up to #350 (testing GitHub Actions is always fun 😅), this brings our workflow into parity with the documentation as described for the action, which uses a
docker://
protocol with theuses
keyword to run a published docker image.If this is left out, the image is built and then run for every action, which is quite time consuming (example: https://github.com/WordPress/openverse-infrastructure/actions/runs/3690796494/jobs/6248175116)
Testing Instructions
Check this against the documentation linked above to make sure there are no other differences.
Checklist
Update index.md
).main
) ora parent feature branch.
errors.
Developer Certificate of Origin
Developer Certificate of Origin