ci: build on GitHub via the mirror, switchable with BUILD_ON

jcoffey-dev commented

2026-09-30 06:18:08 +00:00

Owner

Gitea stays the source of truth and push-mirrors every commit and tag to the GitHub replica. This lets GitHub Actions do the heavy building (native amd64 and arm64 runners) while Gitea keeps releases, announcements and gating.

The switch is the organization variable BUILD_ON, set on both forges:

BUILD_ON=github: .github/workflows/ci.yml runs on GitHub, publishes to the Gitea registry/releases as before, and posts a github/ci (branch|tag) commit status back. Gitea's build jobs skip; a new github job waits for that status, so this repository's Gitea checks still pass or fail with the real result.
BUILD_ON unset: nothing changes. GitHub's jobs skip and Gitea builds exactly as today. This is also the fallback if GitHub is unavailable.

Merging this is inert until the variable is set.

GitHub-era workflows that would misbehave once mirrored (scheduled releases, GHCR publishing and pruning) are removed, as is any dependabot.yml: every mirror sync deletes branches that exist only on GitHub, so its pull requests could never land.

GitHub organization settings this needs: variables BUILD_ON, REGISTRY, GITEA_URL; secret GITEA_TOKEN (write:repository + write:package); the three pinned docker/* actions allowed.

Gitea stays the source of truth and push-mirrors every commit and tag to the GitHub replica. This lets GitHub Actions do the heavy building (native amd64 and arm64 runners) while Gitea keeps releases, announcements and gating. **The switch** is the organization variable `BUILD_ON`, set on both forges: - `BUILD_ON=github`: `.github/workflows/ci.yml` runs on GitHub, publishes to the Gitea registry/releases as before, and posts a `github/ci (branch|tag)` commit status back. Gitea's build jobs skip; a new `github` job waits for that status, so this repository's Gitea checks still pass or fail with the real result. - `BUILD_ON` unset: nothing changes. GitHub's jobs skip and Gitea builds exactly as today. This is also the fallback if GitHub is unavailable. Merging this is inert until the variable is set. GitHub-era workflows that would misbehave once mirrored (scheduled releases, GHCR publishing and pruning) are removed, as is any `dependabot.yml`: every mirror sync deletes branches that exist only on GitHub, so its pull requests could never land. GitHub organization settings this needs: variables `BUILD_ON`, `REGISTRY`, `GITEA_URL`; secret `GITEA_TOKEN` (write:repository + write:package); the three pinned `docker/*` actions allowed.

jcoffey-dev added 1 commit 2026-09-30 06:18:08 +00:00

ci: build on GitHub via the mirror, switchable with BUILD_ON

ci / github (pull_request) Skipped

Details

ci / version (pull_request) Skipped

Details

ci / node (pull_request) Successful in 2m56s

Details

ci / publish (pull_request) Skipped

Details

ci / docker-build (pull_request) Successful in 1m20s

Details

d9fd02256a

Gitea stays the source of truth and push-mirrors every commit and tag to
GitHub. With the organization variable BUILD_ON=github, GitHub's ci.yml runs
the tests, the Docker build check and, on tags, the multi-arch image publish
on native amd64 and arm64 runners, pushing to the Gitea registry and posting a
commit status back. Gitea's build jobs skip, and a new `github` job waits for
that status so the Gitea run still passes or fails with the real result.

With BUILD_ON unset nothing changes: GitHub's jobs skip and Gitea builds as
before, which is also the fallback if GitHub is unavailable.

The GitHub-era release, publish and cleanup workflows are removed -- the
weekly release is cut on Gitea and images no longer go to GHCR -- and so is
dependabot.yml, whose pull request branches every mirror sync would delete.

jcoffey-dev merged commit b5d2c84478 into main

2026-09-30 06:53:06 +00:00

jcoffey-dev deleted branch ci/build-on-github

2026-09-30 06:53:06 +00:00

ci: build on GitHub via the mirror, switchable with BUILD_ON #16