# Other adjustments

Check also the [overview](https://docs.sonarsource.com/sonarqube-server/2025.3/analyzing-source-code/languages/overview "mention") for specific language properties related to analysis scope adjustment.

## Adjusting the secret detection scope <a href="#secret-detection-scope" id="secret-detection-scope"></a>

By default, SonarQube Server detects exposed secrets in all files processed by the language analyzers. You can refine the scope of the secret detection: see [secrets](https://docs.sonarsource.com/sonarqube-server/2025.3/analyzing-source-code/languages/secrets "mention").

## Excluding files over a certain size <a href="#excluding-files-over-certain-size" id="excluding-files-over-certain-size"></a>

You can set the `sonar.filesize.limit` and `sonar.javascript.maxFileSize` properties on the CI/CD host to exclude files over a certain limit. For more information, see [analysis-parameters](https://docs.sonarsource.com/sonarqube-server/2025.3/analyzing-source-code/analysis-parameters "mention").

## Disabling the SCM’s file ignore patterns <a href="#disabling-scm-file-ignore" id="disabling-scm-file-ignore"></a>

Your SonarQube analysis will automatically exclude files that are ignored by your source code control system. For example, in git repositories, it respects the `.gitignore` file. SonarQube also respects the ignore directives used in SVN repositories.

You can disable this behavior by setting the sonar property `sonar.scm.exclusions.disabled` to `true` on the CI/CD host. For more information, see [analysis-parameters](https://docs.sonarsource.com/sonarqube-server/2025.3/analyzing-source-code/analysis-parameters "mention").

## Related pages <a href="#related-pages" id="related-pages"></a>

* [exclude-from-coverage-duplication](https://docs.sonarsource.com/sonarqube-server/2025.3/project-administration/setting-analysis-scope/exclude-from-coverage-duplication "mention")
* [excluding-files-based-on-patterns](https://docs.sonarsource.com/sonarqube-server/2025.3/project-administration/setting-analysis-scope/excluding-files-based-on-patterns "mention")
* [excluding-based-on-file-extension](https://docs.sonarsource.com/sonarqube-server/2025.3/project-administration/setting-analysis-scope/excluding-based-on-file-extension "mention")
* [advanced-exclusions](https://docs.sonarsource.com/sonarqube-server/2025.3/project-administration/setting-analysis-scope/advanced-exclusions "mention")
* [setting-initial-scope](https://docs.sonarsource.com/sonarqube-server/2025.3/project-administration/setting-analysis-scope/setting-initial-scope "mention")
* [verifying-analysis-scope](https://docs.sonarsource.com/sonarqube-server/2025.3/project-administration/setting-analysis-scope/verifying-analysis-scope "mention")
* Adjust the analysis scope [introduction](https://docs.sonarsource.com/sonarqube-server/2025.3/instance-administration/analysis-functions/analysis-scope/introduction "mention")


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sonarsource.com/sonarqube-server/2025.3/project-administration/setting-analysis-scope/other-adjustments.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.