|
Error: Invalid New Code Period (using hash commit as a version)
|
|
1
|
78
|
June 18, 2019
|
|
Upcoming Changes to New Code Period
|
|
4
|
215
|
June 8, 2020
|
|
Improving the Coverag View
|
|
2
|
59
|
May 8, 2020
|
|
Can SonarQube ignore Win/Ux line endings?
|
|
4
|
99
|
April 14, 2020
|
|
How to determine if my change will pass coverage on new code QG
|
|
4
|
87
|
April 1, 2020
|
|
How to configure SonarQube to detect new code compared with current master status
|
|
11
|
1422
|
February 27, 2020
|
|
SonarJS appears to be rescanning entire file if there is no new code/only deleted code
|
|
8
|
262
|
February 18, 2020
|
|
How to calculate coverage on new code even before pushing code to repository?
|
|
5
|
528
|
January 17, 2020
|
|
New Code Coverage are Missing when Submit Code Earlier than Setting ‘sonar.leak.period=BASELINE’
|
|
6
|
433
|
January 2, 2020
|
|
New Code Question
|
|
3
|
94
|
October 16, 2019
|
|
Old issues closed and reopened as new ones
|
|
3
|
327
|
September 19, 2019
|
|
How does SonarQube know a file has changed?
|
|
3
|
137
|
June 27, 2019
|
|
New lines will point to added lines
|
|
1
|
91
|
April 2, 2019
|
|
Aggregate new code coverage by version or over time
|
|
4
|
224
|
March 26, 2019
|
|
Issue reopened as new after changing/reverting rule config
|
|
9
|
218
|
March 19, 2019
|
|
Leak Period Report Same As Overall Report
|
|
10
|
289
|
January 31, 2019
|
|
New bugs appeared on long-lived branch
|
|
1
|
299
|
November 16, 2018
|
|
Old issue became new?
|
|
2
|
186
|
September 12, 2018
|
|
How is SonarQube tracking and charging lines of code
|
|
12
|
5978
|
August 28, 2018
|
|
Does "Some Quality Gate conditions on New Code were ignored because of the small number of New Lines" only appear at the beginning of a new leak period?
|
|
10
|
1163
|
August 20, 2018
|
|
Can not find the blue lines (new since previous version) in new code coverage files
|
|
3
|
346
|
July 18, 2018
|
