mathieudutour / mathieudutour/github-tag-action
Ability to run this in the PR stage
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 733
- Forks
- 227
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I see we can run this in the PR stage but it is not yielding correct version tags according to the contents of the commit message. The default_bump always seems to be patch when we run this on non main/master branch.
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 by reproducing the GitHub Action in a pull-request or non-main branch using commit messages that should produce different version bumps. Read the action's workflow and version-bump entry points to trace how default_bump is selected. Done means PR-stage runs derive the expected version tag from the commit message instead of always selecting patch.
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
- 32/100