From 91494f7823deb7e0e7b55df119595ff89cefef15 Mon Sep 17 00:00:00 2001 From: Manav Rathi Date: Thu, 20 Mar 2025 10:42:42 +0530 Subject: [PATCH] [server] Change server/ghcr => ghcr/server In prep for its new baby sibling, ghcr/web. --- .github/workflows/server-publish.yml | 4 ++-- server/docs/publish.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/.github/workflows/server-publish.yml b/.github/workflows/server-publish.yml index a677fd9eac..5167f8cc4c 100644 --- a/.github/workflows/server-publish.yml +++ b/.github/workflows/server-publish.yml @@ -36,6 +36,6 @@ jobs: username: ${{ github.actor }} password: ${{ secrets.GITHUB_TOKEN }} - - name: Update branch server/ghcr to point to source commit + - name: Update branch ghcr/server to point to source commit run: | - git push -f origin HEAD:refs/heads/server/ghcr + git push -f origin HEAD:refs/heads/ghcr/server diff --git a/server/docs/publish.md b/server/docs/publish.md index 04b1171fcc..b425da750f 100644 --- a/server/docs/publish.md +++ b/server/docs/publish.md @@ -37,7 +37,7 @@ Once the workflow completes, the resultant image will be available at `ghcr.io/ente-io/server`. The image will be tagged by the commit SHA. The latest image will also be tagged, well, "latest". -The workflow will also update the branch `server/ghcr` to point to the commit it +The workflow will also update the branch `ghcr/server` to point to the commit it used to build the image. This branch will be overwritten on each publish; thus -`server/ghcr` will always points to the code from which the most recent ghcr +`ghcr/server` will always points to the code from which the most recent ghcr docker image for museum has been built.