fix(ci): use REGISTRY secrets for container registry login
Some checks failed
Auto Tag on Merge to Main / auto-tag (push) Failing after 2s
CI - Lint and Build / build-frontend (push) Successful in 14s
Release - Build and Publish Docker Images / build-and-publish (push) Successful in 1m9s
CI - Lint and Build / lint-backend (push) Successful in 14s
CI - Lint and Build / lint-frontend (push) Successful in 13s
CI - Lint and Build / docker-build-test (push) Successful in 36s
Some checks failed
Auto Tag on Merge to Main / auto-tag (push) Failing after 2s
CI - Lint and Build / build-frontend (push) Successful in 14s
Release - Build and Publish Docker Images / build-and-publish (push) Successful in 1m9s
CI - Lint and Build / lint-backend (push) Successful in 14s
CI - Lint and Build / lint-frontend (push) Successful in 13s
CI - Lint and Build / docker-build-test (push) Successful in 36s
GITHUB_TOKEN doesn't have container registry permissions in Gitea. Use dedicated REGISTRY_USERNAME and REGISTRY_PASSWORD secrets. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
@@ -30,8 +30,8 @@ jobs:
|
|||||||
uses: docker/login-action@v3
|
uses: docker/login-action@v3
|
||||||
with:
|
with:
|
||||||
registry: tea.millaguie.net
|
registry: tea.millaguie.net
|
||||||
username: ${{ github.actor }}
|
username: ${{ secrets.REGISTRY_USERNAME }}
|
||||||
password: ${{ secrets.GITHUB_TOKEN }}
|
password: ${{ secrets.REGISTRY_PASSWORD }}
|
||||||
|
|
||||||
- name: Build and push backend image
|
- name: Build and push backend image
|
||||||
uses: docker/build-push-action@v5
|
uses: docker/build-push-action@v5
|
||||||
|
|||||||
Reference in New Issue
Block a user