Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions .github/workflows/docker-publish.yml
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@ name: Create and publish a Docker image

on:
push:
branches: ["main"]
branches: ["main", "preview"]

env:
REGISTRY: ghcr.io
Expand Down Expand Up @@ -31,9 +31,9 @@ jobs:
uses: docker/metadata-action@v5
with:
images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
flavor: |
latest=true
tags: |
# set latest tag for main branch only
type=raw,value=latest,enable={{is_default_branch}}
Copy link
Member

@ulgens ulgens Aug 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need to make this dynamic? I believe having a hardcoded "main" is safe enough.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I got the {{is_default_branch}} from the action's documentation: https://github.com/docker/metadata-action?tab=readme-ov-file#latest-tag. I do agree that having a hardcoded main is unlikely to cause issues so I'm happy to change that.

type=ref,event=branch
type=sha

Expand Down