Publish images on GHCR. Closes #10 - #63
Merged
Merged
Conversation
regulartim
marked this pull request as ready for review
September 1, 2026 09:51
Member
Author
|
I can only really test if this works when it is merged into |
opbot-xd
approved these changes
Sep 1, 2026
opbot-xd
left a comment
Collaborator
There was a problem hiding this comment.
Hi Tim! Thanks for the help here, was not very sure with docker publishing. The PR looks good and matches the faithful patterns of greedybear. :D
This file contains hidden or 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.
Description
This adds a workflow for publishing container images on GHCR. Basically an adapted copy of the workflow we use in GreedyBear.
Related issues
Please add related issues: the issues you are trying to solve as well as other issues that are important in the context of this pull request.
Type of change
Checklist
Please complete this checklist carefully. It helps guide your contribution and lets maintainers verify that all requirements are met.
Formalities
<feature name>. Closes #999- Release PRs (develop → main): Title must be the version number (e.g.
0.2.0)develop.develop.- Exception: Release PRs target
main.Docs and tests
Ruff) gave 0 errors.Review process