Skip to content

Publish images on GHCR. Closes #10 - #63

Merged
regulartim merged 2 commits into
developfrom
publish_images
Sep 1, 2026
Merged

Publish images on GHCR. Closes #10#63
regulartim merged 2 commits into
developfrom
publish_images

Conversation

@regulartim

@regulartim regulartim commented Sep 1, 2026

Copy link
Copy Markdown
Member

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

  • Bug fix (non-breaking change which fixes an issue).
  • New feature (non-breaking change which adds functionality).
  • Breaking change (fix or feature that would cause existing functionality to not work as expected).
  • Chore (refactoring, dependency updates, CI/CD changes, code cleanup, docs-only changes).

Checklist

Please complete this checklist carefully. It helps guide your contribution and lets maintainers verify that all requirements are met.

Formalities

  • I chose an appropriate title for the pull request in the form: <feature name>. Closes #999
    - Release PRs (develop → main): Title must be the version number (e.g. 0.2.0)
  • My branch is based on develop.
  • The pull request is for the branch develop.
    - Exception: Release PRs target main.
  • I have reviewed and verified any LLM-generated code included in this PR.

Docs and tests

  • I documented my code changes with docstrings and/or comments.
  • Linter (Ruff) gave 0 errors.
  • I have added tests for the feature/bug I solved.
  • All the tests gave 0 errors.

Review process

  • We encourage you to create a draft PR first, even when your changes are incomplete. This way you refine your code while we can track your progress and actively review and help.
  • If you think your draft PR is ready to be reviewed by the maintainers, click the corresponding button. Your draft PR will become a real PR.
  • Every time you make changes to the PR and you think the work is done, you should explicitly ask for a review. After receiving a "change request", address the feedback and click "request re-review" next to the reviewer's profile picture at the top right.

@regulartim
regulartim marked this pull request as ready for review September 1, 2026 09:51
@regulartim

Copy link
Copy Markdown
Member Author

I can only really test if this works when it is merged into develop. :/

@regulartim
regulartim requested a review from opbot-xd September 1, 2026 09:51

@opbot-xd opbot-xd left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

@regulartim
regulartim merged commit 89663ef into develop Sep 1, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants