From 0e76d1c602fe40073c4bde7573c71c8eb08a0665 Mon Sep 17 00:00:00 2001 From: colin-mueller-sonarsource Date: Mon, 16 Dec 2019 16:48:46 +0100 Subject: [PATCH] DOCS Removed 3 references to old branch model --- server/sonar-docs/src/pages/analysis/pull-request.md | 2 +- server/sonar-docs/src/pages/branches/branches-faq.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/server/sonar-docs/src/pages/analysis/pull-request.md b/server/sonar-docs/src/pages/analysis/pull-request.md index c6712519a87..3bd88ad4681 100644 --- a/server/sonar-docs/src/pages/analysis/pull-request.md +++ b/server/sonar-docs/src/pages/analysis/pull-request.md @@ -20,7 +20,7 @@ A [Quality Gate](/user-guide/quality-gates/) lets you ensure you are meeting you * **Focuses on new code** – The PR quality gate only uses your project's quality gate conditions that apply to "on New Code" metrics. * **Assigns a status** – Each PR shows a quality gate status reflecting whether it Passed or Failed. -PR analyses on {instance} are deleted automatically after 30 days with no analysis. This can be updated in **Administration > Configuration > General > Number of days before purging inactive short living branches**. +PR analyses on {instance} are deleted automatically after 30 days with no analysis. This can be updated in **Administration > Configuration > General Settings > Housekeeping > Number of days before purging inactive branches**. ## Analysis Parameters diff --git a/server/sonar-docs/src/pages/branches/branches-faq.md b/server/sonar-docs/src/pages/branches/branches-faq.md index 9b7adeab9e8..7af486490e0 100644 --- a/server/sonar-docs/src/pages/branches/branches-faq.md +++ b/server/sonar-docs/src/pages/branches/branches-faq.md @@ -9,7 +9,7 @@ _Branch analysis is available as part of [Developer Edition](https://redirect.so Branches will be deleted automatically when they are inactive according to your settings at [Administration > Configuration > General Settings > Housekeeping > Number of days before deleting inactive branches](/#sonarqube-admin#/admin/settings?category=housekeeping) except for branches you have set to be kept when inactive. These branches are kept until you delete them manually at the project level at **Administration > Branches & Pull Requests**. See the [Branches Analysis](/branches/overview/) for more information on keeping inactive branches. ## Does my project need to be stored in an SCM like Git or SVN? -No, you don't need to be connected to a SCM. But if you use Git or SVN we can better track the new files on short-lived branches and so better report new issues on the files that really changed during the life of the short-lived branch. +No, you don't need to be connected to a SCM. However, SCM data still enhances the SonarQube exprerience (including issue auto-assignment and issue backdating), and you will be well prepared to take advantage of [Pull Request Analysis](/analysis/pull-request/)! ## What if I mark an Issue "Won't Fix" or "False-Positive" in a branch? It will be replicated as such when creating a Pull Request and merging the Pull Request into the master branch. @@ -21,7 +21,7 @@ You can delete a branch in the **Branches** tab at **Project Settings > Branches Yes, an extra node called "branch" is added to the payload. ## When are Webhooks called? -When the computation of the background task is done for a given branch but also when an issue is updated on a short-lived branch. +When the computation of the background task is done for a given branch. ## What is the impact on my LOCs consumption vs my license? The LOC of your largest branch are counted toward your license limit. All other branches are ignored. -- 2.39.5