You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default entire file gets scanned for rules, Can we get an option to identify new code vs existing code and rules will be applied only on new code, this will help in identifying the issues reported by CFLint on new code only and issues on existing code will be ignored.
We have an option of Base version in SonarServer, can we get similar option for CFLint where it can be integrated with GIT repo which will be considered as base code to check against with.
We do have an option for Line level or rule level ignore but that's change in exiting code which we want to avoid
The text was updated successfully, but these errors were encountered:
yogeshsGIT
changed the title
Add new option to identify old vs existing code
Add new option to identify new vs existing code
Mar 4, 2022
By default entire file gets scanned for rules, Can we get an option to identify new code vs existing code and rules will be applied only on new code, this will help in identifying the issues reported by CFLint on new code only and issues on existing code will be ignored.
We have an option of Base version in SonarServer, can we get similar option for CFLint where it can be integrated with GIT repo which will be considered as base code to check against with.
We do have an option for Line level or rule level ignore but that's change in exiting code which we want to avoid
The text was updated successfully, but these errors were encountered: