Skip to content

Skip Docker image builds on forks without their own registry - #20

Merged
QuicksilverSlick merged 1 commit into
mainfrom
chore/docker-skip-on-forks
Sep 11, 2026
Merged

Skip Docker image builds on forks without their own registry#20
QuicksilverSlick merged 1 commit into
mainfrom
chore/docker-skip-on-forks

Conversation

@QuicksilverSlick

Copy link
Copy Markdown
Owner

Why

On this fork the Docker image workflow fails on every push to main and on every same-repo pull request: it builds relay images and tries to push them, or its build cache, to ghcr.io/block/buzz, which a fork cannot write to (denied: permission_denied).

Change

build, push-gateway-build and qualify now run only when github.repository == 'block/buzz' || vars.GHCR_IMAGE != ''. The two merge jobs depend on the builds, so they skip with them.

  • Upstream: unchanged.
  • This fork: the workflow skips, because nothing here uses these images (Dreamforge connects to a hosted relay).
  • A fork that wants its own images: sets GHCR_IMAGE, the variable the workflow already reads, and it runs.

Three lines plus a comment, so future upstream merges stay easy. Written as a PR because this session isn't permitted to change repository settings, so disabling the workflow wasn't available.

🤖 Generated with Claude Code

The Docker image workflow publishes to ghcr.io/block/buzz unless the repo
variable GHCR_IMAGE names another registry. On a fork that has not set it,
every push to main and every same-repo pull request fails: the build tries to
push to Block's registry, or to its build cache, and is denied.

build, push-gateway-build and qualify now run only upstream, or on a fork that
has set GHCR_IMAGE. The merge jobs need the builds, so they skip with them.
Upstream behaviour is unchanged, and a fork that wants its own images opts in
by setting the variable the workflow already reads.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@QuicksilverSlick
QuicksilverSlick merged commit db9625e into main Sep 11, 2026
142 of 151 checks passed
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