Add workflow for devs to create debug images from PRs #115
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.
Per the title, this does what it says.
After merge we'll have a workflow we can navigate to under "Actions". And once there we can type, or paste, in a PR number. The workflow will then check out that PR and identify the current head commit for it. Then it will produce a dev/debug image for the changes included in that PR and push to ghcr.io.
This can be helpful for quickly testing the changes in a PR before merge. And given that the images only exist on GHCR.io it will not pollute the dockerhub. So it should be relatively low risk to introduce these dev focused images without confusing them with customer/end-user ones in docker hub.
Once the workflow completes it should update the PR with a comment and links to the images with the names of the tags it produced. Any subsequent image for the same PR will use the same rolling tag, but all past images will exist at static tags correlated to their commit hash too.