From e952699f4d013b228ee24a72da01faae20ece9d1 Mon Sep 17 00:00:00 2001 From: CrazyMax Date: Wed, 23 Sep 2020 11:04:40 +0200 Subject: [PATCH] Fix CI workflow and README Signed-off-by: CrazyMax --- .github/workflows/ci.yml | 2 +- README.md | 5 +++-- 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 11618c4..ed78c32 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -92,7 +92,7 @@ jobs: localhost:5000/name/app:latest localhost:5000/name/app:1.0.0 secrets: | - GIT_AUTH_TOKEN=01234567890abcdefgh + GIT_AUTH_TOKEN=${{ github.token }} - name: Inspect run: | diff --git a/README.md b/README.md index 5bcbd20..b7a683f 100644 --- a/README.md +++ b/README.md @@ -80,8 +80,9 @@ jobs: run: echo ${{ steps.docker_build.outputs.digest }} ``` -If you want to authenticate against a private repository, you have to use a secret named `GIT_AUTH_TOKEN` to be able -to authenticate against it with buildx: +Building from current repository automatically uses the [GitHub Token](https://help.github.com/en/actions/configuring-and-managing-workflows/authenticating-with-the-github_token) +as provided by `secrets` so it does not need to be passed. But if you want to authenticate against another private +repository, you have to use a secret named `GIT_AUTH_TOKEN` to be able to authenticate against it with buildx: ```yaml -