docker / docker/metadata-action
Support `merge_group` events for `type=ref` tags
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.1k
- Forks
- 160
- Avg merge
- 4d 17h
- Merged PRs (30d)
- 12
Description
Description
Github Merge Queue is a common part of a CI/CD flow nowadays. In our case the test suite triggered by the Merge Queue relies on the existence of a Docker image. For us it only makes sense to tag it with the PR number that went into the Merge Queue so we could also benefit from layer cache later on.
It'd be really nice to have a type=ref,event=mq tag option, similar to the type=ref,event=pr one.
Currently, our workaround is type=raw,value=pr-${{ <PR Number> }},enable=${{ github.event_name == 'merge_group' }} where the PR number is extracted from github.event.merge_group.head_ref.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing type=ref,event=pr handling and the tag-generation entry point. Compare the merge_group event data, including github.event.merge_group.head_ref, with the current workaround; done means type=ref,event=mq produces a tag containing the merged pull request number.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, typescript
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100