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.
resolve annotated tag
See original GitHub issueSee #15. Don’t worry about [ creating / reading / deleting ] tags just yet. Just be able to parse them enough so that resolveRef can do its job, so that @mojavelinux can do his tree walking.
Issue Analytics
- State:
- Created 5 years ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
ResolveRevision doesn't resolve annotated tags · Issue #772
It seems like git rev-parse would resolve to the hash of the tag object in this case. So we probably want to mimic...
Read more >Git - git-tag Documentation
Tag objects (created with -a , -s , or -u ) are called "annotated" tags; they contain a creation date, the tagger name...
Read more >`type commit` in an annotated tag in git
Yes: an annotated tag object can point to another annotated tag object ... "resolve a tag to its object", i.e., peel off all...
Read more >Annotated and Lightweight Git Tags
Annotated tags store extra metadata such as author name, release notes, tag-message, and date as full objects in the Git database. All this...
Read more >Git Create Tag Guide {Annotated and Lightweight}
Annotated tags are usually used for public releases as they contain detailed metadata about the tagger and an optional message about the commit....
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 issue has been resolved in version 0.22.2 🎉
The release is available on:
Your semantic-release bot 📦🚀
You’re always a wealth of information. I’m learning more about git from you each day. Since you’re matching what the plain-text format returns, then it makes sense to maintain that compatibility. It might be something to mention in the type information.