Closed Stephan202 closed 2 months ago
Looks good. No mutations were possible for these changes. Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.
Looks good. No mutations were possible for these changes. Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code
Stumbed upon this PR today.
I looked up https://docs.sonarsource.com/sonarcloud/administering-sonarcloud/advanced-administration/#domain-whitelists and the one you added is listed there
it also mentions analysis-sensorcache-eu-central-1-prod.s3.amazonaws.com
BTW harden-runner
allows use of wildcards as well, so you can also use *.sonarcloud.io
if you want.
Hey @varunsh-coder! Great timing; I received an email about this a few days ago, and had just started work on #1271 :smile: The wildcard is a good idea; will consider :muscle:
Ah, question then: I suppose that *.sonarcloud.io
won't capture sonarcloud.io
, right? (And similarly for *.github.com
and github.com
.)
Right. You will need to specify both *.sonarcloud.io
and sonarcloud.io
if you want to allow api.sonarcloud.io
(and similar subdomains) and sonarcloud.io
.
Based on this report.
Suggested commit message: