mathieudutour / mathieudutour/github-tag-action
Still creating new releases when no commits present
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 733
- Forks
- 227
- PR merge metrics
- No merged PRs in 30d
Description
The readme says that if no commits are present, new_tag should be undefined. However it appears that when no commits are present, it is using default_bump instead.
Output from GitHub Actions run:
Specifically these logs:
Previous tag was v0.2.0, previous version was 0.2.0.
Analysis of 0 commits complete: no release
New version is 0.3.0.
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 README's description of new_tag and the GitHub Actions output showing analysis of zero commits. Trace where default_bump is used when no commits are present, then reproduce a no-commit run; done means no new release is created and new_tag remains undefined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github-actions, typescript
- Domain
- ci-cd, release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100