Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Auto created tag v13.0.1-beta.1 after v13-beta release
See original GitHub issuev13.0.1-beta.1 tag gets auto created on each v13-beta releases.
The release gets created by @sahil28297.
I delete it manually because it creates v13.0.1-beta.1 tag on docker.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
[Release Notes] ERPNext v13-Beta.11 and Frappe v13-Beta.10
v13.0.1-beta.1 tag gets auto created on each v13-beta releases. The release gets created by @sahil28297. I delete it manually because it ...
Read more >About auto-tagging - Google Ads Help
Auto -tagging is a feature that you need to turn on before you can do the following: Track conversions on your website on...
Read more >tag already exists in the remote" error after recreating the git tag
The work-around is to delete the tag (and tick remove all remotes). Then create the same tag and push.
Read more >Git - Tagging - Git SCM
In this section, you'll learn how to list existing tags, how to create and delete tags, and what the different types of tags...
Read more >Managing releases using Git tags and semantic versioning
Speaker: Mike Miles From module development to site building releasing code into a production environment is a process teams want to make ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This is happening because this tag is deleted only on the remote and not from the local machine, and with each release this deleted tags gets pushed again onto the remote. @saurabh6790 Please run
git fetch --prune --tagson your local repository once the tag is deleted from the remote to sync the tags on the remote and local machines. Refer this for other answers if the above command doesn’t work.I deleted this tag again,
@sahil28297 should I just write github action to delete release?
Ideally,
step 1 : change to frappe app directory
step 2 : list tags
step 3: confirm
v13.0.1-beta.1tag exists and delete itThis has to be done on @saurabh6790’s release-bench