mathieudutour / mathieudutour/github-tag-action
If there is no tag on a repo, the script won't generate any tags or Changelog.
Open
Nobody has claimed this yet.
bug
good first issue
help wanted
- Dominant language
- TypeScript
- Stars
- 733
- Forks
- 227
- PR merge metrics
- No merged PRs in 30d
Description
After a lot of trying and error, I found an issue (maybe it's not a bug but a feature) when pushing code to a repository without tags. The parser will say there are no new commits, so it won't generate any new versions.
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
No files or tests are named. Reproduce the action on a repository with no tags, then trace the parser and version-generation entry points to find why it reports no new commits. Done means an untagged repository produces the intended initial tag and changelog, with coverage for that case.
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
- Needs clarification
- Newbie friendliness
- 35/100