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.
GitHub release/tag is not perfect
See original GitHub issueMore of a note to me.
Currently we get the “first in response array” tag/release. The Babel example is perferct for showing the problem.
I think with /github/release/owner/repo we should show latest stable release/tag. In the case with Babel latest one happens to be a “prerelease”, so it shows it in orange.
I’m thinking for this
/github/release/owner/reposhould show lastest stable release (e.g. Babel’s v6), in blue/github/release/owner/repo/prereleaseshow latest prerelease
Or what about /github/prerelease/owner/repo for the prereleases and /github/release for the stable ones?
Perfect would be /github/release and /github/prerelease, because this will allow for static github badges like /github/release/owner/repo/v1.2.3 … which… actually, not make much sense because you can just /badge/release/v1.2.3/color ;d
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:10 (10 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Finally got this
So this issue applies those ideas to npm badges too 😆
/npm/v/micromatch- thelatest(default)/npm/v/micromatch/latest- same as above/npm/v/ava/next- thenextdist-tag/npm/v/foobar/whatever- thewhateverdist-tag