Introducing New Clean as You Code criteria
|
|
14
|
1557
|
May 2, 2025
|
Clean As You Code statistics showing too little issues
|
|
6
|
45
|
October 11, 2024
|
Some new development branch issues are not reported in pull-request scan
|
|
1
|
44
|
August 27, 2024
|
Quickly identifying parent branch issues relating to a pull-request scan
|
|
8
|
80
|
August 2, 2024
|
Missing Code Smells in New Code
|
|
1
|
177
|
June 21, 2024
|
Is there a plan to detect folder name changes?
|
|
7
|
157
|
June 20, 2024
|
[Webinar] Clean as You Code: A Proactive Approach to Technical Debt
|
|
1
|
218
|
May 24, 2024
|
Fix your Quality Gates today to maximise impact
|
|
5
|
990
|
March 13, 2024
|
Process - Out of scope issue handling with CleanAsYouGo
|
|
3
|
263
|
February 8, 2024
|
How does SonarQube decide when to enforce a 'Clean as you Code' rule on edited old code?
|
|
3
|
211
|
January 30, 2024
|
New Quality Gates come with Clean as You Code conditions
|
|
0
|
287
|
January 22, 2024
|
[Webinar] Clean as You Code: No pain, lots to gain
|
|
1
|
617
|
November 17, 2023
|
SonarLint for VS Code 3.22 - Focus on new code, new secret types, file/directory exclusions
|
|
2
|
826
|
November 13, 2023
|
SonarLint for Eclipse 8.1 - Focus on new code, even more secret detection rules
|
|
1
|
741
|
November 6, 2023
|
SonarLint for IntelliJ 9.1 - Focus on new code, new secret types, quick fixes preview
|
|
0
|
863
|
October 9, 2023
|
Clean as Code bug?
|
|
1
|
222
|
September 29, 2023
|
New Code Definition setup is now part of project onboarding
|
|
0
|
903
|
August 4, 2023
|