From: G. Ann Campbell Date: Tue, 2 Apr 2019 19:00:56 +0000 (-0400) Subject: DOC [SONAR-11880] add `.gitignore` to Narrowing... X-Git-Tag: 7.8~456 X-Git-Url: https://source.dussan.org/?a=commitdiff_plain;h=66930246f477d60ebca901cd03192ab92725e4ee;p=sonarqube.git DOC [SONAR-11880] add `.gitignore` to Narrowing... --- diff --git a/server/sonar-docs/src/pages/project-administration/narrowing-the-focus.md b/server/sonar-docs/src/pages/project-administration/narrowing-the-focus.md index 7f9e8134661..fd08062b173 100644 --- a/server/sonar-docs/src/pages/project-administration/narrowing-the-focus.md +++ b/server/sonar-docs/src/pages/project-administration/narrowing-the-focus.md @@ -17,7 +17,7 @@ If {instance}'s results aren't relevant, no one will want to use it. That's why You can make these changes globally or at a project level. At both levels, the navigation path is the same: **Administration > General Settings > Analysis Scope**. ## Ignore Files -We recommend that you exclude generated code, source code from libraries, etc. There are four different ways to narrow your analysis to the source code that will be relevant to the development team. You can combine them all together to tune your analysis scope. +We recommend that you exclude generated code, source code from libraries, etc. There are four different ways to narrow your analysis to the source code that will be relevant to the development team. You can combine them all together to tune your analysis scope. Additionally, we automatically exclude from analysis the files described in your projects' `.gitignore` files. This behavior can be disabled. See `sonar.scm.exclusions.disabled` in the [Analysis Parameters](/analysis/analysis-parameters/) page for details. ### Source Directories Set the [sonar.sources](/analysis/analysis-parameters/) property to limit the scope of the analysis to certain directories.