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

Merge pull request #241 from crazy-max/fix-readme

Browse Source 
Fix README
This commit is contained in:
CrazyMax 2020-11-30 13:32:46 +01:00 committed by GitHub
commit d51711af0d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@ -59,8 +59,8 @@ build-secrets, remote cache, etc. and different builder deployment/namespacing o
### Git context ### Git context
The default behavior of this action is to use the [Git context invoked](https://github.com/docker/build-push-action/blob/master/src/context.ts#L31-L35) The default behavior of this action is to use the Git context invoked by your workflow.
by your workflow. (eg. `https://github.com/<owner>/<repo>.git#<ref>`)
```yaml ```yaml
name: ci name: ci
@ -116,8 +116,8 @@ repository, you have to use a secret named `GIT_AUTH_TOKEN` to be able to authen
GIT_AUTH_TOKEN=${{ secrets.MYTOKEN }} GIT_AUTH_TOKEN=${{ secrets.MYTOKEN }}
``` ```
> :warning: Subdir for Git context is [not yet supported](https://github.com/docker/build-push-action/issues/120). > :warning: Subdir for Git context is not yet supported ([moby/buildkit#1684](https://github.com/moby/buildkit/issues/1684))
> For the moment you can use the [path context](#path-context). > but you can use the [path context](#path-context) in the meantime.
> More info: https://docs.docker.com/engine/reference/commandline/build/#git-repositories > More info: https://docs.docker.com/engine/reference/commandline/build/#git-repositories