Skip to content

[3.0] Fix coverage report check#2544

Merged
Exanite merged 3 commits intodevelop/3.0from
fix/coverage-reports
Jan 24, 2026
Merged

[3.0] Fix coverage report check#2544
Exanite merged 3 commits intodevelop/3.0from
fix/coverage-reports

Conversation

@Exanite
Copy link
Member

@Exanite Exanite commented Jan 24, 2026

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%! 🎉

@github-actions
Copy link
Contributor

File Coverage
All files 14%

Minimum allowed coverage is 0%

Generated by 🐒 cobertura-action against 862e197

@Exanite Exanite marked this pull request as ready for review January 24, 2026 03:15
@Exanite Exanite requested a review from a team as a code owner January 24, 2026 03:15
@github-project-automation github-project-automation bot moved this from Todo to In Progress in Silk.NET Development Tracker Jan 24, 2026
@Exanite Exanite merged commit 9ded1ed into develop/3.0 Jan 24, 2026
30 checks passed
@Exanite Exanite deleted the fix/coverage-reports branch January 24, 2026 03:19
@github-project-automation github-project-automation bot moved this from In Progress to Done in Silk.NET Development Tracker Jan 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants