Repository navigation
docs: README badges in the standard order - #12
Merged
Merged
Conversation
The badges follow repo-standards STANDARD.md section 9.
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
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 README badges in the order and form of repo-standards' STANDARD.md section 9, the same in every repository: how to get it, whether
mainis healthy, how it is secured, and what it is.Workflow badges are GitHub's own for
main; every link is absolute, since PyPI does not rewrite relative links; alt texts follow the standard. The tagline moves below the badges, which sit directly under the title.Every badge image was fetched and renders a value. The repo-standards rescan, which now checks this, passes.