actions/docker-build-push
1
0
Fork 0
mirror of https://github.com/docker/build-push-action.git synced 2024-11-06 00:35:53 -05:00
Code Issues Projects Releases Packages Wiki Activity

Update examples with docker/metadata-action

Browse source 
Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com>
This commit is contained in:
CrazyMax 2021-05-10 18:01:34 +02:00
parent 17822e4df4
commit 3a090ce0da
No known key found for this signature in database
GPG key ID: 3248E46B6BB8C7F7
3 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
.github/workflows/e2e.yml vendored
View file

@ -59,7 +59,7 @@ jobs:
-
name: Docker meta
id: meta
uses: crazy-max/ghaction-docker-meta@v2
uses: docker/metadata-action@v3
with:
images: ${{ matrix.slug }}
-

2
.github/workflows/example.yml vendored
View file

@ -29,7 +29,7 @@ jobs:
-
name: Docker meta
id: meta
uses: crazy-max/ghaction-docker-meta@v2
uses: docker/metadata-action@v3
with:
images: ${{ env.DOCKER_IMAGE }}
tags: |

4
docs/advanced/tags-labels.md
View file

@ -2,7 +2,7 @@
If you come from [`v1`](https://github.com/docker/build-push-action/tree/releases/v1#readme) and want an
"automatic" tag management and [OCI Image Format Specification](https://github.com/opencontainers/image-spec/blob/master/annotations.md)
for labels, you can do it in a dedicated step. The following workflow will use the [Docker meta action](https://github.com/crazy-max/ghaction-docker-meta)
for labels, you can do it in a dedicated step. The following workflow will use the [Docker metadata action](https://github.com/docker/metadata-action)
to handle tags and labels based on GitHub actions events and Git metadata.
```yaml
@ -30,7 +30,7 @@ jobs:
-
name: Docker meta
id: meta
uses: crazy-max/ghaction-docker-meta@v2
uses: docker/metadata-action@v3
with:
# list of Docker images to use as base name for tags
images: |