aboutsummaryrefslogtreecommitdiffstats
path: root/server/sonar-docs/src/pages/analysis/scm-integration.md
diff options
context:
space:
mode:
Diffstat (limited to 'server/sonar-docs/src/pages/analysis/scm-integration.md')
-rw-r--r--server/sonar-docs/src/pages/analysis/scm-integration.md16
1 files changed, 16 insertions, 0 deletions
diff --git a/server/sonar-docs/src/pages/analysis/scm-integration.md b/server/sonar-docs/src/pages/analysis/scm-integration.md
new file mode 100644
index 00000000000..78a498f9c81
--- /dev/null
+++ b/server/sonar-docs/src/pages/analysis/scm-integration.md
@@ -0,0 +1,16 @@
+---
+title: SCM Integration
+url: /analysis/scm-integration/
+---
+
+Collecting SCM data during code analysis can unlock a number of SonarQube features:
+
+* Automatic Issue Assignment
+* code annotation (blame data) in the Code Viewer
+* SCM-driven detection of new code (to help with [Fixing the Water Leak](/user-guide/fixing-the-water-leak/)). Without SCM data, SonarQube determines new code using analysis dates (to timestamp modification of lines).
+
+### Turning it on/off
+SCM integration requires support for your individual SCM provider. Git and SVN are supported by default. <!-- sonarqube -->For other SCM providers, see the Marketplace.<!-- /sonarqube -->
+
+If need be, you can toggle it off at global/project level via administration settings.
+