Skip to content

ci: enable GHCR docker image push in Node CI#3

Merged
kubo6472 merged 1 commit into
mainfrom
cursor/enable-ghcr-docker-push-ccbf
Jun 15, 2026
Merged

ci: enable GHCR docker image push in Node CI#3
kubo6472 merged 1 commit into
mainfrom
cursor/enable-ghcr-docker-push-ccbf

Conversation

@kubo6472

Copy link
Copy Markdown
Member

Summary

Enables automatic Docker image publishing to GitHub Container Registry (ghcr.io) in the Node CI workflow.

Previously, GHCR push was gated behind a GHCR_ENABLED repository secret and also required DockerHub secrets to be present. This change makes GHCR push work out of the box for the official Sofie-Automation/sofie-core repository.

Changes

  • Remove dependency on the GHCR_ENABLED secret
  • Decouple GHCR push from DockerHub secret availability
  • Push to GHCR on main, release* branches, and version tags (v**)
  • Limit GHCR push to the Sofie-Automation org and push events (not PRs/forks)
  • Apply to both build-core and build-gateways jobs

Images published

Image Registry path
Server Core ghcr.io/sofie-automation/sofie-core-server-core
Playout Gateway ghcr.io/sofie-automation/sofie-core-playout-gateway
MOS Gateway ghcr.io/sofie-automation/sofie-core-mos-gateway
Live Status Gateway ghcr.io/sofie-automation/sofie-core-live-status-gateway

DockerHub publishing behavior is unchanged and still requires the existing DockerHub secrets.

Notes

  • Uses GITHUB_TOKEN with packages: write permission (already configured on the build jobs)
  • The GHCR_ENABLED secret is no longer needed and can be removed from repository settings
Open in Web Open in Cursor 

Remove the GHCR_ENABLED secret gate and push images to ghcr.io
automatically on main, release branches, and tags for the official
Sofie-Automation repository. GHCR push no longer depends on DockerHub
secrets and uses GITHUB_TOKEN for authentication.

Images pushed:
- ghcr.io/sofie-automation/sofie-core-server-core
- ghcr.io/sofie-automation/sofie-core-{playout-gateway,mos-gateway,live-status-gateway}

Co-authored-by: Jakub Doboš <kubo6472@users.noreply.github.com>
@coderabbitai

coderabbitai Bot commented Jun 15, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@kubo6472, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 4 minutes and 9 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 43268ba6-be09-445f-b9df-5cf7f47a8a04

📥 Commits

Reviewing files that changed from the base of the PR and between 4712f46 and 728f76e.

📒 Files selected for processing (1)
  • .github/workflows/node.yaml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch cursor/enable-ghcr-docker-push-ccbf

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@kubo6472
kubo6472 marked this pull request as ready for review June 15, 2026 17:25
@kubo6472
kubo6472 merged commit a0d0fc5 into main Jun 15, 2026
44 checks passed
@kubo6472
kubo6472 deleted the cursor/enable-ghcr-docker-push-ccbf branch June 15, 2026 17:36
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.

2 participants