The suggested default branch example does not work for schedule

[felipecrs]

tags: |
  type=raw,value=latest,enable=${{ github.ref == format('refs/heads/{0}', github.event.repository.default_branch) }}

Here is an example:

https://github.com/felipecrs/jenkins-agent-dind/blob/master/.github/workflows/ci.yml#L35

https://github.com/felipecrs/jenkins-agent-dind/runs/5964649319?check_suite_focus=true#step:3:31

I would say that this variable does not get filled properly for schedule events, which is meaningful, as metadata-action relies on it.

[felipecrs]

While the best would be for GitHub to fix it, I wonder if we should do something to make users aware of it before recommending it, or to use another approach.

[felipecrs]

Perhaps this: https://github.com/pipeline-foundation/get-origin-def-branch

[crazy-max]

Can you add this step in your workflow and give me the output if possible please?: https://github.com/crazy-max/ghaction-dump-context#usage

[felipecrs]

https://github.com/felipecrs/ghaction-dump-context/actions/workflows/ci.yml

There you go.

[felipecrs]

repository isn't set in such occasion.

[crazy-max]

Ok so looking at their docs, schedule event always runs on the default branch:

Scheduled workflows run on the latest commit on the default or base branch.

So I would say add this:

tags: |
  type=raw,value=latest,enable=${{ github.ref == format('refs/heads/{0}', github.event.repository.default_branch) || github.event_name == 'schedule' }}

But I think we could add a global expression named is_default_branch to ease the integration in your workflow:

tags: |
  type=raw,value=latest,enable={{is_default_branch}}

WDYT?

[felipecrs]

I think that the first approach would be fine, if we knew that schedule is the only outlier. I wonder what happens for other events, as there are many.

PS: I did it for my repository, as I know that I don't use anything but schedule, push and pull_request.

Having this said, I would conclude that this is not a reliable manner of obtaining the default branch at all (it's not even documented), and because of that, the second approach would be better indeed.

I would even add the is_default_branch to the list of outputs of the action, so that it can be also consumed in other parts of the workflow. As an useful helper.

[crazy-max]

I think that the first approach would be fine, if we knew that schedule is the only outlier. I wonder what happens for other events, as there are many.

I have many fixtures too that covers most of them or at least most important imo: https://github.com/docker/metadata-action/tree/master/__tests__/fixtures

[crazy-max]

I would even add the is_default_branch to the list of outputs of the action, so that it can be also consumed in other parts of the workflow. As an useful helper.

This action is not a general purpose one for other steps and only exposes what it does. It should be done upstream by GitHub.

[felipecrs]

Absolutely understood.

[crazy-max]

@felipecrs You can test with crazy-max/docker-metadata-action@default-branch. See #192. Docs has also been updated: https://github.com/crazy-max/docker-metadata-action/tree/default-branch#global-expressions. Let me know if that sgty.

[felipecrs]

@crazy-max that's awesome. I made a few suggestions in the PR btw.