To reduce friction especially in codebases burdened with technical debt Clayton offers a smart filter called the Legacy Code Filter, part of its Protect What’s New strategy.
The toggle is available on Git repositories for every branch code review report generated by Clayton.
What is a reference date
The reference date acts as a historical marker, allowing you to refine which issues are reported. When you set a reference date, you're essentially telling the tool to ignore any code quality problems that existed in the codebase before that specific date. This strategic filtering helps your team ignore issues introduced prior to that date, thereby highlighting only new issues going forward. It effectively reduces the noise from legacy technical debt, allowing your team to stay focused on improving the quality of recent code changes and ensuring a more efficient review process.
How to Set the Reference Date
You can set the reference date for an individual repository by navigating to Settings for that org and locating the Reference Date option. Any issue introduced before this date will be treated as legacy code and excluded from scans when the Legacy Code Filter is enabled.
How to Turn On and Off the Legacy Code Filter
You can enable or disable the Legacy Code Filter for each repository using the toggle switch located in the top right corner of the repository view. This toggle is visible across several tabs Overview, Issues, and Branches, changing the setting in any one of these tabs will automatically apply it across all the others.
Note: This feature is not available for Salesforce org scans.