No description
  • Dockerfile 100%
Find a file
Jonatan Zint 7b3291c01c
All checks were successful
Build and Push Image / build-and-push (push) Successful in 1m2s
add reusable step and repo linkage
2026-03-02 09:09:18 +01:00
.forgejo add reusable step and repo linkage 2026-03-02 09:09:18 +01:00
Dockerfile fix: shortnames 2026-02-21 10:24:21 +01:00
README.md add reusable step and repo linkage 2026-03-02 09:09:18 +01:00

Builder Image + Reusable Forgejo Action

This repository publishes forgejo.zint.de/l0rn/builder:latest and exposes a reusable Forgejo Action for building and pushing OCI images with podman.

Reusable action (Forgejo-compatible)

Use this in any Forgejo project workflow:

name: Build and Push

on:
  push:
    branches: [main]
    tags: ["v*"]
  workflow_dispatch:

permissions:
  contents: read
  packages: write

jobs:
  build-and-push:
    runs-on: docker
    container:
      image: forgejo.zint.de/l0rn/builder:latest
    steps:
      - uses: actions/checkout@v4
      - uses: l0rn/builder/.forgejo/actions/build-and-push@main
        with:
          registry_token: ${{ secrets.FORGEJO_REGISTRY_TOKEN }}

Repo linkage in Forgejo packages

The action writes OCI labels including:

  • org.opencontainers.image.source=${GITHUB_SERVER_URL}/${GITHUB_REPOSITORY}
  • org.opencontainers.image.url=${GITHUB_SERVER_URL}/${GITHUB_REPOSITORY}

These labels allow Forgejo to associate the pushed image/package with the repository that triggered the workflow.