Merged
Conversation
Contributor
|
Minimum allowed coverage is Generated by 🐒 cobertura-action against 862e197 |
curin
approved these changes
Jan 24, 2026
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 of the PR
Technically a duplicate of #2543, but this is to test if the coverage report comment works for PRs coming from branches from the dotnet/Silk.NET repo. It currently does not work for forks (known issue), but the comment does work for the main repo.
This fixes the coverage report check, making it so that all checks pass.
Related issues, Discord discussions, or proposals
N/A
Further Comments
The last time coverage reports ran was during #2494.
In that PR we had 3% coverage, now we have 14%! 🎉