Forgejo Action: build and publish Docker image on merge to main #25
Loading…
Reference in a new issue
No description provided.
Delete branch "mailship-7o9-forgejo-action-build-publish-docker-imag-63e"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
mailship-7o9
Add a Forgejo Actions workflow that builds the mailship Docker image on every merge to main and publishes it to the Forgejo container registry. Serves the README's self-hosting path (
docker pull) and future pull-based deploys.Changes
.forgejo/workflows/docker-publish.yml— New Forgejo Action triggered onpushtomain. Checks out the repo, sets up Docker Buildx, authenticates toforgejo.lorentz.isviasecrets.GITHUB_TOKEN, then builds and pushes the image with two tags:forgejo.lorentz.is/matt/mailship:latestforgejo.lorentz.is/matt/mailship:${{ github.sha }}The workflow is separate from the existing
ci.yml(which runs checks on every push/PR) since it has a different trigger and concern — publishing the image only when code reaches main.How to test
Merge this PR to main, then verify the workflow runs in the Forgejo Actions tab. After a successful run, confirm the images appear at
forgejo.lorentz.is/matt/mailship: