Show tags in commit history
See original GitHub issueAdd a link to a tag that is set on a commit when looking at the commit history. This makes it easier to identify new commits that haven’t been released yet, or identify change ranges.
I realize you can use the pull request/diffing UI for that, but that’s way more complicated than looking at the history, especially when a tag only includes a few commits. Plus you need to know the tag name in to compare, since those are not auto completed by the UI.
IssueHunt Summary
dotconnor has been rewarded.
Backers (Total: $65.00)
Submitted pull Requests
Tips
- Checkout the Issuehunt explorer to discover more funded issues.
- Need some help from other developers? Add your repositories on IssueHunt to raise funds.
IssueHunt has been backed by the following sponsors. Become a sponsor
Issue Analytics
- State:
- Created 6 years ago
- Reactions:36
- Comments:23 (15 by maintainers)
Top Results From Across the Web
Show tags in commit history · Issue #807
This makes it easier to identify new commits that haven't been released yet, or identify change ranges.
Read more >Github: show tags in commits history
To show the tags that contain a commit (i.e. tags the precede a commit): git tag --contains <commit>.
Read more >How to List, Create, Remove, and Show Tags in Git
To view all the created tags in alphabetical order: git tag To get more ... First, run git log to find out the...
Read more >Git - Tagging
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 >How To List Git Tags
In order to list and sort Git tags by their latest Git activity, you can use the “git tag” command with the “–sort=committerdate”....
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
@hkdobrev I have waaay to much experience with graphQL.
I helped @k0shk0sh build FastHub we spent 2 months trying to switch to V4 and we ended up reverting the whole thing. If it was me I would wait another 4-5 months. Lately they have been adding many more typical things. IMHO it’s worth the wait
With the API we could query the repo’s refs (paged) and match them to whatever commits are visible on the current page. It probably wouldn’t require more than 1-2 extra HTTP requests per commit page, which is fine for me.
This is definitely a feature I’d like and use. I don’t mind finally seeing API integration, we already even have a GHE API URL helper