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.
Release tags
See original GitHub issueI’d like to suggest annotating your release tags with a short description of the changes for that version. This is useful when running git tag -n. Right now they all show [ci skip], which makes it difficult to navigate to a previous version if needed.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
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 >About releases - GitHub Docs
Releases are based on Git tags, which mark a specific point in your repository's history. A tag date may be different than a...
Read more >Git - Tagging - Git SCM
The -m specifies a tagging message, which is stored with the tag. If you don't specify a message for an annotated tag, Git...
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 >Managing Releases with Semantic Versioning and Git Tags
Michael Miles from MIT Sloan shares how to manage software releases with semantic versioning and Git tags. Learn about build numbers and how...
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
It has been finally fixed, thx again for your feedback!
@aking7 we will add the message as well, thx!