Hi community, Recently I’ve added to my project .editorconfig file in order to ignore some of SonarCloud issues. I followed this advice Excluding files in certain directories for SonarScanner for .NET - SonarCloud - Sonar Community (sonarsource.com) Here are my Azure DevOps tasks: steps: - tas…

Hi there, Partially I found out what was the problem. I hope it helps someone else in the future. The problem was with the dotnet build command I was missing the reference other .editorconfig file in the .sln file. The only thing is that the pipelines are working on the PR builds but not on the one…

Hello @ABinkowskiATDOCOsoft , Do you have the same behavior if you run it locally? Where is your .editorconfig file located relatively from your files that raises S1144? Based on where your file is located, it might not apply to some files. For instance, if your .editorconfig is not in a parent f…

Hi @sebastien.marichal Sorry for the late response. I have not run it locally. Here is the structure of my editor config files . ├── .editorconfig ├── /src └── /tests/ └── /ExampleMicroservice/ ├── /src/ │ └── /DOCOsoft.ExampleMicroservice.Domain/ │ ├── .edito…

Hello @ABinkowskiATDOCOsoft , I have been doing more investigation on this issue. It seems that in the particular case of S1144 (and S4487), it does not work. The severity is ignored for some reason. This seems to be only the case when invoking our analyzer with SonarScanner for .NET. I have crea…

is the new S6418 also affected by this? I can’t get it to ignore errors raised in the appsettings.json file. Other rules seem to work.

As I answered on your other thread on this problem , S6418 in a json file is not handled by the .NET analyzers and so cannot be disabled using an editorconfig file.

As part of onboarding a new large project I’ve also discovered the following rules seem to suffer from the same issue: S107 S110 S1144 S1192 S2077 S2245 S2259 S2342 S2436 S2583 S2589 S3655 S3776 S4158 S4487 S4790 S5332 S5443 S6418 S7130

Hi @chris.coleman , I think this is what you’re looking for: [image] Question on .editorconfig is correctly handled by SonarQube SonarQube Server / Community Build Hello @lxb , The Scanner for .NET does not seem to properly pick up the settings in the .editorconfig. I ha…

We are seeing this for non-SQ rules as well, specifically IDE0007 which we have set to ‘suggestion’ but shows up as an issue in SQ. Since this isn’t a SQ rule, the only way we can turn it off is if we set it to ‘none’ in our .editorconfig which is not what we want to do.

Hi @austinmcdaniel , Welcome to the community! You’ve resurrected a topic that’s minimum 5 months old. Per the FAQ , please don’t do that. Please create a new thread with all your details. Thx, Ann

Sonar cloud - Ignoring rules with editorconfig is not working

SonarQube Cloud

ganncamp (G Ann Campbell) February 10, 2025, 5:22pm 17

Hi @chris.coleman,

I think this is what you’re looking for:

HTH,
Ann

1 Like

Topic		Replies	Views
Rules set to none or suggestion in EditorConfig show up as warnings during dotnet build SonarQube Cloud sonarqube , scanner , dotnet	2	167	December 19, 2024
Question on .editorconfig is correctly handled by SonarQube SonarQube Server / Community Build dotnet	4	528	December 24, 2024
Connecting SonarCloud to a VS Project that uses StyleCop stops the .editorconfig file taking effect Visual Studio visualstudio , sonarqube-ide	2	1688	May 30, 2022
Rules settings in .editorConfig file is not used by sonar scanner SonarQube Server / Community Build sonarqube , scanner , dotnet , bump	3	323	August 5, 2025
Disable C# rules and exclude files from analysis SonarQube Cloud	8	5959	July 20, 2023

Sonar cloud - Ignoring rules with editorconfig is not working

Related topics