mathieudutour / mathieudutour/github-tag-action
Annotation count up
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 733
- Forks
- 227
- PR merge metrics
- No merged PRs in 30d
Description
Hello Mathieu,
I'm using the github-tag-action with annotated tags as following:
- name: Bump version and push tag
id: tag_version
uses: mathieudutour/github-tag-action@v5.1
with:
github_token: ${{ secrets.GITHUB_TOKEN }}
release_branches: master, RC
create_annotated_tag: true
I get also release-tags like this:
$ git tag -l
v0.8.0-RC.0
v1.0.0-RC.0
v1.0.1-RC.0
v1.0.2-RC.0
v1.0.3-RC.0
v1.0.4-RC.0
As you can see the annotation does'nt count up (RC.0).
Is this what is expected? Because then I don't know why there is a trailing number (.0).
My expectation is actually that RC.n will count up.
Thanks
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
Reproduce the reported workflow using github-tag-action@v5.1 with annotated tags and the shown release_branches configuration, then trace the tag-generation entry point in the TypeScript action. Confirm whether repeated RC releases remain at RC.0 or increment, and document or test the expected RC.n behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github-actions, typescript
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100