format and release: out with BK, in with GHA #55
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this change?
Move the format and release workflows to GHA to align with the other TF modules
BK pipeline infra removed wellcomecollection/buildkite-infrastructure#29
How to test
On push to any branch but main, the format workflow should run in GHA.
BK pipeline should not run
How can we measure success?
GHA reduce the need for extra scripts and docker stuff
This contributes to our platform health OKR
Have we considered potential risks?
The release workflow has not been tested e2e in the wild. However it mirrors that of
scala-libswhich is working fine