Repository navigation
docs: add release, build and license badges to the README - #56
Merged
Merged
Conversation
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.
Summary
Brings the repository README in line with the other Purview-Dev project READMEs by adding a badge row at the top.
v0.8.0). The site publishes no NuGet package (release.ymlusesrelease-mode: GitHubRelease), so a GitHub release version badge replaces the NuGet badge the sibling repos use.deploy.ymlworkflow (runs the fulljust validate+ build onmain).LICENSE.md).Notes
README.mdis not consumed by the build (nothing reads it).format-check(oxfmt, scoped tosrc/) passes; unit tests: 341 pass / 0 fail.gh repo editand are not part of this diff.