Skip to content

docs: name both registries the template publishes to - #32

Merged
ElianCodes merged 1 commit into
mainfrom
docs/name-the-published-images
Oct 1, 2026
Merged

ElianCodes merged 1 commit into
mainfrom
docs/name-the-published-images

Conversation

@ElianCodes

Copy link
Copy Markdown
Contributor

The README mentioned only GHCR, but docker-publish.yml has always pushed to Docker Hub as well — so a new module scaffolded from this template inherits a README that undersells where its image lands.

Keeps the <module-name> placeholder, since this is the template and the name is genuinely per-module, and points at the IMAGE_NAME env that controls it.

Worth knowing for anyone scaffolding from here: new GHCR packages are created private by default, so the GHCR line only works after flipping the package to public in its settings. The Docker Hub push is public from the first release.

The README mentioned only GHCR, but docker-publish.yml pushes to Docker
Hub as well. Keeps the `<module-name>` placeholder, since it is the
template, and points at the `IMAGE_NAME` that controls it.
@ElianCodes
ElianCodes merged commit b2c18a5 into main Oct 1, 2026
1 check passed
@ElianCodes
ElianCodes deleted the docs/name-the-published-images branch October 1, 2026 11:02
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.

1 participant