SonarQube for IntelliJ (GoLand) plugin version: 11.6.0.83783
GoLand version: 2025.2.5
Programming language you’re coding in: go
Is connected mode used: No
And a thorough description of the problem / question:
In my project, I have many HTML templates used for sending emails. Because they need to stay compatible with various email clients, they contain outdated HTML practices. I tried excluding all HTML files by adding the glob pattern **/*.html under SonarQube for IDE → Project Settings → File Exclusions → Exclude using GLOB, but it doesn’t work. Whether I run Analyze with SonarLint on the project root, use Analyze All Project Files from the plugin options, or analyze directly from the template files, the HTML files are still included in the analysis.
When triggering an analysis on the full project, it is considered a forced analysis, in which case we do not take into account file exclusions.
Normally, if you open a file that you excluded, it should not be analyzed automatically anymore, and you will see the message This file is not automatically analyzed.
Thank you very much for the quick response. As you mentioned, the message “This file is not automatically analyzed” correctly appears for files that match the conditions configured in Files Excluded. I understand the current logic that Files Excluded only applies to automatic analysis.
However, I believe it would be important to be able to run a full manual analysis of the entire application while still excluding the files listed in Files Excluded. In fact, this is the option I would personally use the most, as I would expect excluded files to always be excluded. It might be worth considering making this behavior configurable—perhaps by adding a checkbox under Files Excluded to indicate whether this configuration should also apply to manual analyses.
