mathieudutour / mathieudutour/github-tag-action
Reference already exists
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 733
- Forks
- 227
- PR merge metrics
- No merged PRs in 30d
Description
My workflow ran successfully once before this. So Previous tag should be v0.0.1. But every push to main now can't detect existing v0.0.1 tag and tries create it again. This workflow is triggered by a push to main branch, I tested the same workflow in another branch is it is working fine.
`Run mathieudutour/github-tag-action@v6.0
with:
github_token: ***
default_bump: patch
release_branches: main
custom_release_rules: hotfix:patch,bug:patch,fix:patch,feat:minor,perf:major
default_prerelease_bump: prerelease
tag_prefix: v
create_annotated_tag: false
fetch_all_tags: false
dry_run: false
Previous tag was v0.0.0, previous version was 0.0.0.
Analysis of 0 commits complete: no release
New version is 0.0.1.
New tag after applying prefix is v0.0.1.
.
Error: Reference already exists`
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 Actions workflow invocation and its reported settings, especially fetch_all_tags: false and the existing v0.0.1 tag. Reproduce a push to main after a prior successful run, then trace how existing tags are detected and confirm completion when v0.0.1 is not recreated and the Reference already exists error is gone.
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
- Needs clarification
- Newbie friendliness
- 35/100