Add Codecov coverage shield to the README build status#419
Merged
Conversation
Coverage has been uploaded to Codecov since the coverage workflow landed, but the README never surfaced it. Follows the aiopurpleair badge pattern: a Coverage shield in the Build Status block, with the shield and link definitions kept in the file's existing alphabetical order. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #419 +/- ##
========================================
Coverage 66.89% 66.89%
========================================
Files 13 13
Lines 1160 1160
Branches 108 108
========================================
Hits 776 776
Misses 338 338
Partials 46 46 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a Codecov coverage badge to the README’s Build Status badge block so readers can see current coverage alongside the existing release and last-commit status.
Changes:
- Add a third badge line for Coverage in the Build Status block.
- Add
coverage-linkandcoverage-shieldreference definitions, keeping the existing reference-definition alphabetical ordering.
Merged
ptr727
added a commit
that referenced
this pull request
Jul 18, 2026
Promotion of the current `develop` integration state to `main`. ## Contents | Area | Change | | --- | --- | | Analyzer conformance | #418 -- removed the repo-wide `dotnet_analyzer_diagnostic` relaxation, fixed the 29 `xUnit1051` sites it hid | | Docs | #419 -- Codecov coverage shield in the README build status block | | Repo config | #417 -- repo-config carry refresh and self-audit carry | ## Conformance issues resolved Closes #380 Closes #387 #380 (xUnit v3 + AwesomeAssertions, `ILoggerFactory` seam) was already satisfied in the tree -- verified rather than assumed: 0 `Assert.*` remaining against 245 `.Should()` calls, `xunit.v3` 3.2.2 pinned with no v2 package, zero Serilog references in the library, and `Utilities/LogOptions.cs` matching the LanguageTags reference seam. #387's four findings were likewise already addressed except finding 1 (analyzer suppression hygiene), which #418 closes. Every remaining suppression was independently probed by removing it and rebuilding, and all proved load-bearing (`CA1711`, `CA1707`, `CA1515`, `NoWarn IL3058`). ## Release impact: no auto-publish This promotion carries **no shipped input**. Per [WORKFLOW.md](../blob/main/WORKFLOW.md) the inclusion list is `Utilities/**`, `version.json`, `Directory.Build.props`, `Directory.Packages.props`; this diff is confined to tests, docs, CI, and repo config: ``` .editorconfig .github/workflows/merge-bot-pull-request.yml AUDIT.md README.md UtilitiesTests/*.cs repo-config/* spec/secrets.json ``` `Utilities/**` is byte-identical between `main` and `develop`, so the published package is already current and merging this will correctly **not** trigger a stable release.
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.
Coverage has been uploaded to Codecov since the coverage workflow landed (#377), but the README never surfaced it.
Adds a Coverage shield to the Build Status block, following the badge pattern used in aiopurpleair:
Shield and link definitions were inserted in the file's existing alphabetical order, between
commits-linkandgithub-link.Verification
coverage: 67%), notunknowncspell.jsonchange needed:codecovis not flagged (aiopurpleair carries the same badge with no dictionary entry), and README is in the CI spell-check scope per CODESTYLE