Git release tags kc-12-b1 and kc-11-b1 point to the latest SNAPSHOT
See original GitHub issueHello, it seems that both release tags actually point to the same commit bumping the release to the next snapshot kc-12-b2
(3d6dca6).
They should point to respective release commit instead:
kc-11-b1
-> 6032b19efb331357c484e66bb714a919cfe99122kc-12-b1
-> c452d75d8491ae9f37a94d06951bc95dd7b6a8c4
Thanks for your work, I’ll hope to be able to test it soon!
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Git - Tagging - Git SCM
Like most VCSs, Git has the ability to tag specific points in a repository's history as being important. Typically, people use this functionality...
Read more >Git Tag: A Complete Guide to Managing Your Snapshots
This post is a detailed introduction to Git Tag including what it is and why we need it. We will also walk through...
Read more >A Tutorial for Tagging Releases in Git - DEV Community
Tags are a simple aspect of Git, they allow you to identify specific release versions of your code. You can think of a...
Read more >Git Tag Release Management - phoenixNAP
Learn how to manage a git release tag to see the official program versions on your project page in this easy to follow...
Read more >git tag | Atlassian Git Tutorial
Git tag command is the primary driver of tag: creation, modification and deletion. Learn how you can use them to organize code and...
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 FreeTop 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
Top GitHub Comments
Okay the tags should be fixed now. Thanks. I would have never noticed this since my local setup was okay…
I do not know how this happened. When I look at my local repository it looks like this:
But after a new checkout I can verify what you see. Big question is how this happened…