diff options
| author | michaelbirnstiehl <michael.birnstiehl@sonarsource.com> | 2019-11-24 18:56:17 -0600 |
|---|---|---|
| committer | SonarTech <sonartech@sonarsource.com> | 2019-12-09 20:46:18 +0100 |
| commit | 2fb4e3512f289f548abe13a27aeb7b38e4e199c5 (patch) | |
| tree | bfc1695f9f895bd1ee5fcee986a603c08265ca4c /server/sonar-docs/src/pages/project-administration/new-code-period.md | |
| parent | 3b2f458bfdf779d929cb82a3fe5a5c0c6765612d (diff) | |
| download | sonarqube-2fb4e3512f289f548abe13a27aeb7b38e4e199c5.tar.gz sonarqube-2fb4e3512f289f548abe13a27aeb7b38e4e199c5.zip | |
SONAR-12708 Update docs for single branch concept
Diffstat (limited to 'server/sonar-docs/src/pages/project-administration/new-code-period.md')
| -rw-r--r-- | server/sonar-docs/src/pages/project-administration/new-code-period.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/server/sonar-docs/src/pages/project-administration/new-code-period.md b/server/sonar-docs/src/pages/project-administration/new-code-period.md index 55575babe6d..f4887b179b1 100644 --- a/server/sonar-docs/src/pages/project-administration/new-code-period.md +++ b/server/sonar-docs/src/pages/project-administration/new-code-period.md @@ -23,11 +23,11 @@ You can set a project's New Code Period to the following: * **Number of days** – Specify a number of days for a floating New Code Period. For example, setting **Number of Days** to 30 creates a floating New Code Period beginning 30 days from the current date. * **Specific analysis** – Choose a previous analysis as your New Code Period. The New Code Period will show any changes made since that analysis. - **Note:** For Community Edition, you can set the New Code Period to a specific past analysis at the project-level because Community Edition doesn't support multiple branches. [Developer Edition](https://redirect.sonarsource.com/editions/developer.html) and [above](https://www.sonarsource.com/plans-and-pricing/) let you set the New Code Period to a specific analysis at the branch level. Each long-lived branch can be set to one of the branch's specific past analyses. See the following section for information on setting a branch-level New Code Period. + **Note:** For Community Edition, you can set the New Code Period to a specific past analysis at the project-level because Community Edition doesn't support multiple branches. [Developer Edition](https://redirect.sonarsource.com/editions/developer.html) and [above](https://www.sonarsource.com/plans-and-pricing/) let you set the New Code Period to a specific analysis at the branch level. Each branch can be set to one of the branch's specific past analyses. See the following section for information on setting a branch-level New Code Period. ### Setting a branch-level New Code Period _Branch analysis is available as part of [Developer Edition](https://redirect.sonarsource.com/editions/developer.html) and [above](https://www.sonarsource.com/plans-and-pricing/)._ -For projects with multiple long-lived branches, you can set a New Code Period for each branch from the **Actions** column of the branches table on the project's **New Code Period** settings page. +For projects with multiple branches, you can set a New Code Period for each branch from the **Actions** column of the branches table on the project's **New Code Period** settings page. You can set a branch's New Code Period to the following: |