Show marketplace and build status in the README - #4
Merged
Conversation
Two badges under the title, linking through to their run histories. The CI badge is pinned to main so that a red pull request does not read as a broken project. The release badge deliberately is not: that workflow is triggered by tags, and tag runs belong to no branch, so the same filter would leave it permanently reading "no status". These are GitHub's own workflow badges rather than shields.io because the readme renders on the marketplace too, which strips badges from domains it does not trust. github.com is on its approved list, qualified as "from Workflows only", which is exactly what these are. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Both link to the marketplace listing, and sit ahead of the build badges: what is published is what a reader wants first, and CI is for whoever is about to change it. These come from badgen.net rather than shields.io, which has retired its Visual Studio Marketplace endpoints — the shields URLs now answer 200 with a "retired badge" placeholder rather than failing, so they would have looked fine right up until the readme rendered. badgen.net is on the marketplace's approved list and returns live figures. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
sachinsachdeva
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Four badges under the title.
main, so a red pull request does not read as a broken projectPublished-state badges come first — that is what a reader wants to know; CI is for whoever is about to change something.
On the sources
The readme renders on the Marketplace as well as GitHub, and the Marketplace strips badges from domains it does not trust. Both sources here are on its approved list:
github.comis, qualified as "from Workflows only", which is exactly what these are, and so isbadgen.net.Not shields.io: it has retired its Visual Studio Marketplace endpoints. They answer
200with a "retired badge" placeholder rather than failing, so they would have looked fine right up until the readme rendered.All four URLs verified against the live listing —
v2.0.0, install count,CI — passing,Release — passing.🤖 Generated with Claude Code