From 7bdbc5f85b29a0293c1ca92c5552e93d5a51af04 Mon Sep 17 00:00:00 2001 From: "G. Ann Campbell" Date: Tue, 6 Nov 2018 15:22:10 -0500 Subject: [PATCH] add reference & links to LLBs, SLBs, PRs --- server/sonar-docs/src/pages/analysis/overview.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/server/sonar-docs/src/pages/analysis/overview.md b/server/sonar-docs/src/pages/analysis/overview.md index 6aa11afa5c0..6535e80bc2d 100644 --- a/server/sonar-docs/src/pages/analysis/overview.md +++ b/server/sonar-docs/src/pages/analysis/overview.md @@ -52,7 +52,7 @@ A project is created in the platform automatically on its first analysis. Howeve ## What does analysis produce? {instance} can perform analysis on 20+ different languages. The outcome of this analysis will be quality measures and issues (instances where coding rules were broken). However, what gets analyzed will vary depending on the language: -* On all languages, "blame" data will automatically be imported from supported SCM providers. Git and SVN are supported automatically. Other providers require additional plugins. +* On all languages, "blame" data will automatically be imported from supported SCM providers. [Git and SVN are supported automatically](/analysis/scm-integration/). Other providers require additional plugins. * On all languages, a static analysis of source code is performed (Java files, COBOL programs, etc.) * A static analysis of compiled code can be performed for certain languages (.class files in Java, .dll files in C#, etc.) * A dynamic analysis of code can be performed on certain languages. @@ -61,7 +61,10 @@ A project is created in the platform automatically on its first analysis. Howeve By default, only files that are recognized by a language analyzer are loaded into the project during analysis. For example if your SonarQube instance had only SonarJava SonarJS on board, all .java and .js files would be loaded, but .xml files would be ignored. - + +## What about branches and pull requests? +_Developer Edition_ adds the ability to analyze your project's release / [long-lived branches](/branches/long-lived-branches/), feature / [short-lived branches](/branches/short-lived-branches/), and [pull requests](/analysis/pull-request/) as well as the ability to automatically decorate pull requests in some SCM interfaces. For more on branches see the [branches overview](/branches/overview/). +