actions/build-push-action
2
0
Fork 0
mirror of https://github.com/docker/build-push-action.git synced 2024-11-27 05:09:03 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix CI workflow and README

Browse Source 
Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com>
This commit is contained in:
CrazyMax 2020-09-23 11:04:40 +02:00
parent 32351da9d7
commit e952699f4d
No known key found for this signature in database
GPG Key ID: 3248E46B6BB8C7F7
2 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.github/workflows/ci.yml vendored
View File

@ -92,7 +92,7 @@ jobs:
localhost:5000/name/app:latest localhost:5000/name/app:latest
localhost:5000/name/app:1.0.0 localhost:5000/name/app:1.0.0
secrets: | secrets: |
GIT_AUTH_TOKEN=01234567890abcdefgh GIT_AUTH_TOKEN=${{ github.token }}
- -
name: Inspect name: Inspect
run: | run: |

5
README.md
View File

@ -80,8 +80,9 @@ jobs:
run: echo ${{ steps.docker_build.outputs.digest }} 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 Building from current repository automatically uses the [GitHub Token](https://help.github.com/en/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)
to authenticate against it with buildx: 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 ```yaml
- -