Remove the SonarCloud scanner workflow and document Automatic Analysi… - #12
Merged
Merged
Conversation
…s as the mode sonar.yml could never succeed. A CI scanner and SonarCloud's Automatic Analysis are mutually exclusive, and which one is active is a server-side project setting that no file in this repository can change. With Automatic Analysis left on, every run of the workflow failed at `sonarscanner end` with "You are running CI analysis while Automatic Analysis is enabled" and published nothing — so the check has been red on every push while contributing no analysis. Remove it rather than keep a permanently failing check. .sonarcloud.properties becomes the only Sonar configuration and keeps both exclusions, so the Uno app findings that the build-less analysis cannot judge still close. Docs follow the reality: - R-9 is rewritten from "the scan never publishes" to what is now an accepted trade-off, with the two costs stated plainly (no coverage, no compiled C# analysis) and instructions to reverse the decision — flip the setting AND restore the workflow from history, or neither. - 7.6 replaces the workflow table row with a table of the two analyses that run without a workflow file, and the local SonarAnalyzer run is promoted to the authoritative check for C# rules. - Correct a standing error: arc42 documented a codeql.yml that does not exist. CodeQL runs via GitHub default setup (dynamic/github-code-scanning/codeql), which is also why the README's CodeQL badge rendered no status — it pointed at a workflow file. Point it at the security tab instead. - Drop the README coverage badge. Coverage has never had a value, and without a scanner it never will. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
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
1 participant
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.
…s as the mode
sonar.yml could never succeed. A CI scanner and SonarCloud's Automatic Analysis are mutually exclusive, and which one is active is a server-side project setting that no file in this repository can change. With Automatic Analysis left on, every run of the workflow failed at
sonarscanner endwith "You are running CI analysis while Automatic Analysis is enabled" and published nothing — so the check has been red on every push while contributing no analysis. Remove it rather than keep a permanently failing check..sonarcloud.properties becomes the only Sonar configuration and keeps both exclusions, so the Uno app findings that the build-less analysis cannot judge still close.
Docs follow the reality: