mathieudutour / mathieudutour/github-tag-action

Bump RC version number on the right at pre_release_branches.

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

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
733
Forks
227
PR merge metrics
No merged PRs in 30d

Description

Hi everyone,
I use composer, and I need to bump the RC version as default behavior on prerelease branches.

**Expected**
v1.1-RC1
v1.1-RC2

Actual Output:
v1.1-RC.0
v1.2-RC.0

Do we have a specific way to do that?
Could be responsibility of the dev to explicitly say what they want to create as a RC, but will be fine if default is RC${n}

**Implementation:**
- name: Tag Bump version and push tag
id: tag_version
uses: mathieudutour/github-tag-action@v5.4
with:
github_token: ${{ secrets.GITHUB_TOKEN }}
pre_release_branches: staging
append_to_pre_release_tag: RC

output 2 runs
v1.1-RC.0
v1.2-RC.0

Any recommendations?

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

Start with the GitHub Actions configuration using pre_release_branches and append_to_pre_release_tag, then inspect how the action produces the shown tags for successive runs. Done means prerelease tags follow the requested RC1, RC2 format rather than RC.0, while preserving the expected version increments.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.