mathieudutour / mathieudutour/github-tag-action
Set Major. Minor, or Patch Release
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 733
- Forks
- 227
- PR merge metrics
- No merged PRs in 30d
Description
Dear all,
I recently integrated this with my project.
This project already has manual releases and tags.
the latest one is v.1.12.0
How do I continue the sequence when using this action?
Can i force it to use v.1.13.0 on the next run?
Please help.
Thank you in advance.
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
The issue names no file, test, or entry point. Start by locating the action's version and tag configuration documentation, then check how an existing v1.12.0 tag is handled. Done means documenting whether a manual starting version such as v1.13.0 is supported and showing the required configuration or workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github-actions, typescript
- Domain
- ci-cd, release
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100