Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: SonarCloud Coverage #513

Merged
merged 1 commit into from
Feb 12, 2024
Merged

Conversation

Zac-Digital
Copy link
Contributor

SonarCloud has some hard dependencies with dotnet-coverage 17.9.3, updating it caused the coverage to always report as 0%, this PR rolls back the update to fix it.

Copy link

Quality Gate Passed Quality Gate passed

Issues
0 New issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

@Zac-Digital Zac-Digital merged commit c047d10 into development Feb 12, 2024
16 checks passed
@Zac-Digital Zac-Digital deleted the fix/sonarcloud-coverage branch February 12, 2024 11:23
Copy link
Contributor

🎉 This PR is included in version 1.6.0-pre-dev.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Copy link
Contributor

🎉 This PR is included in version 1.6.0-development.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants