mathieudutour / mathieudutour/github-tag-action
Issue on Revert commit
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 733
- Forks
- 227
- PR merge metrics
- No merged PRs in 30d
Description
## **Current behavior**
try to make a revert commit, but when I try I receive this error:
Run mathieudutour/github-tag-action@v5.6
Previous tag was v9.8.0, previous version was 9.8.0.
Analyzing commit: update readme
The commit should not trigger a release
Analyzing commit: revert: nueva caracteristica
This reverts commit 6fbab30
The commit should not trigger a release
Analyzing commit: revert: feat: nueva caracteristica
This reverts commit 6fbab302ed676a9c23c960f80cd1c45f7aba1f62
The commit should not trigger a release
Analysis of 3 commits complete: no release
Error: Could not increment version.
## **Expected behavior**
First commit: "feat: nueva caracteristica"
Al correct on semantic release and new tag was created
Second commit: "revert: feat: nueva caracteristica" commit messaje: This reverts commit 6fbab302ed676a9c23c960f80cd1c45f7aba1f62
This should have continued the semantic release process and not give an error, I´m not entirely clear about the expected behavior but clearly it should not be an error.
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 with the github-tag-action@v5.6 run shown in the issue and reproduce the version-increment failure using the listed feature and revert commits. Trace why the revert analysis produces no release and then an increment error; done means the revert follows the expected semantic-release behavior without this error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github-actions, typescript
- Domain
- ci-cd, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100