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 It Does
Once you set a reference date, Clayton will:
Ignore issues introduced before that date
Highlight only new issues going forward
Reduce noise from legacy technical debt
Help your team stay focused on improving the quality of recent code changes
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, Branches, and Pull Requests—and 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.
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.
