README: Status section badges corrected - #502
Merged
Merged
Conversation
swapnilpaliwal-sd
added
the
documentation
swapnilpaliwal-sd
added a commit
that referenced
this pull request
Sep 19, 2026
…o note was wrong (#502)
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.
The note claiming workflow badges do not render on a private repository was wrong and is removed. The Engines badge pointed at a workflow that has never run (publish-npm.yml, #478), so GitHub served nothing; until the first publish it is a static badge linking to #478. The Build badge is unchanged: it reads "no status" until ci.yml has run on main (#418); its label is that workflow's name.