Skip to content

Migrate CI image publishing from Docker Hub to GitHub Container Registry#1

Draft
Copilot wants to merge 2 commits intomasterfrom
copilot/move-to-enterprise
Draft

Migrate CI image publishing from Docker Hub to GitHub Container Registry#1
Copilot wants to merge 2 commits intomasterfrom
copilot/move-to-enterprise

Conversation

Copy link

Copilot AI commented Feb 28, 2026

The CI pipeline was pushing Docker images to Docker Hub under a hardcoded personal account (wurstbrot) using an external HUB_TOKEN secret — not appropriate for an enterprise setup.

Changes

  • Registry: Docker Hub → ghcr.io (GitHub Container Registry)
  • Auth: secrets.HUB_TOKEN + hardcoded username → secrets.GITHUB_TOKEN + github.actor (no manual secret management required)
  • Image tags: wurstbrot/dsomm*ghcr.io/${{ github.repository_owner }}/dsomm*
  • Permissions: Added packages: write to the job to allow GHCR pushes
- name: Log in to GitHub Container Registry
  uses: docker/login-action@v2
  with:
    registry: ghcr.io
    username: ${{ github.actor }}
    password: ${{ secrets.GITHUB_TOKEN }}

Images are now owned by the repository's organization/owner, authenticated via the automatically-provisioned GITHUB_TOKEN, with access control managed through GitHub's permission model.


💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

Co-authored-by: LGLenz <68009202+LGLenz@users.noreply.github.com>
Copilot AI changed the title [WIP] Move application to enterprise setup Migrate CI image publishing from Docker Hub to GitHub Container Registry Feb 28, 2026
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