Forgejo Action: build and publish Docker image on merge to main #25

Merged
matt merged 2 commits from mailship-7o9-forgejo-action-build-publish-docker-imag-63e into main 2026-09-18 17:40:38 +00:00
Collaborator

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 on push to main. Checks out the repo, sets up Docker Buildx, authenticates to forgejo.lorentz.is via secrets.GITHUB_TOKEN, then builds and pushes the image with two tags:
    • forgejo.lorentz.is/matt/mailship:latest
    • forgejo.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:

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 on `push` to `main`. Checks out the repo, sets up Docker Buildx, authenticates to `forgejo.lorentz.is` via `secrets.GITHUB_TOKEN`, then builds and pushes the image with two tags: - `forgejo.lorentz.is/matt/mailship:latest` - `forgejo.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`:
hudson added 1 commit 2026-09-18 16:32:37 +00:00
feat: add Forgejo Action workflow to build and publish Docker image
All checks were successful
CI / checks (pull_request) Successful in 36s
5deace1967
Add a Forgejo Actions workflow (docker-publish.yml) that builds the
mailship Docker image on every merge to main and publishes it to the
Forgejo container registry at forgejo.lorentz.is/matt/mailship.

Tags pushed: :latest and :<commit-sha>

Serves the README's self-hosting path (docker pull) and future
pull-based deploys.
matt added 1 commit 2026-09-18 17:40:28 +00:00
Update .forgejo/workflows/docker-publish.yml
All checks were successful
CI / checks (pull_request) Successful in 37s
cab5cab6fa
matt merged commit dbe4f6741d into main 2026-09-18 17:40:38 +00:00
matt deleted branch mailship-7o9-forgejo-action-build-publish-docker-imag-63e 2026-09-18 17:40:41 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: matt/mailship#25
No description provided.