mirror of
https://github.com/docker/build-push-action.git
synced 2024-11-06 00:35:53 -05:00
Fix CI workflow and README
Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com>
This commit is contained in:
parent
32351da9d7
commit
e952699f4d
2 changed files with 4 additions and 3 deletions
2
.github/workflows/ci.yml
vendored
2
.github/workflows/ci.yml
vendored
|
@ -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: |
|
||||
|
|
|
@ -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
|
||||
-
|
||||
|
|
Loading…
Reference in a new issue