docker / docker/metadata-action

Would you consider ref tag type without event?

Open
#253 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

kind/enhancement
Dominant language
TypeScript
Stars
1.1k
Forks
160
Avg merge
4d 17h
Merged PRs (30d)
12

Description

Behaviour
Steps to reproduce this issue

Execute the action with only the ref tag type:
tags: | type=ref

Expected behaviour

Depending on the event, it should select the appropriate event type.
On a tag push, select the tag event type.
On a branch push, select the branch event type.

Actual behaviour

For now it fails with Missing event attribute for type=ref

Configuration
  • Repository URL (if public):
  • Build URL (if public):
on:
  push:
jobs:
  demo:
    steps:
      # Setup
      - uses: actions/checkout@2541b1294d2704b0964813337f33b291d3f8596b  # v3.0.2
      - uses: docker/metadata-action@57396166ad8aefe6098280995947635806a0e6ea  # v4.1.1
        with:
          images: my_dummy_image
          tags: |
            type=ref
Logs

Download the log file of your build
and attach it to this issue.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is named. Start by locating the tags input parsing and event-resolution entry points, then reproduce the configuration on push events for both a tag and a branch; done means type=ref works without an event attribute and selects the matching event type.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, typescript
Domain
ci-cd, tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.