chore: Revert using SHAs in GitHub workflows #1706
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.
Describe the pull request
Thank you for contributing to the project!
Please use this template to help us handle your PR smoothly.
What
It reverts using SHAs instead of version numbers in our GitHub workflows.
Why
Using SHAs is a good idea (see this for more info), but our organisation GitHub Action allowlist uses version number currently, which means the Actions using SHAs are blocked. We have to change the allowlist first before implementing this again.
How
Copy-pasting the old values back. I couldn't revert the files in their entirety, because I wanted to keep some of the changes.
Checklist
Before submitting your pull request, please ensure you have done the following. Check each checkmark if you have done so or if it wasn't necessary: