semver based on branch names

Open
#98 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
docker, git, github-actions, typescript
Domain
ci-cd, devops, release

Research direction

Start by reviewing the existing type=semver, type=pattern, and type=ref,event=branch behavior described in the issue. Define how a branch such as refs/heads/release/v1.2.3 should produce 1.2.3 and 1.2, then verify the behavior through the action's existing validation path and documentation.

Written by the indexing model from the issue text.

Description

I'd like to kick off semver tags based on git branch names, as opposed to git tag names.

For example:

push refs/heads/release/v1.2.3 1.2.3, 1.2

It doesn't seem like this is possible with type=semver since that only works on git tags. type=pattern likewise doesn't apply. type=ref,event=branch, while applying to branches, doesn't allow custom patterns.

Any help would be much appreciated!

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

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.

More from docker/metadata-action

All issues in docker/metadata-action

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.