[I] Sonar linter should only take effect on the new code [kvrocks]

["git-hulk (via GitHub)" <gi...@apache.org>]

git-hulk opened a new issue, #1866:
URL: https://github.com/apache/kvrocks/issues/1866

   ### Search before asking
   
   - [X] I had searched in the [issues](https://github.com/apache/kvrocks/issues) and found no similar issues.
   
   
   ### Version
   
   https://github.com/apache/kvrocks/pull/1863/checks?check_run_id=18276090339
   
   
   The duplicate code error is not related to the PR, guess we should enable the option that only checks the new code.
   
   ### Minimal reproduce step
   
   None
   
   ### What did you expect to see?
   
   Sonar lint only takes effect on the new code.
   
   ### What did you see instead?
   
   Scanned the full repo.
   
   ### Anything Else?
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [X] I'm willing to submit a PR!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@kvrocks.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] Sonar linter should only take effect on the new code [kvrocks]

["git-hulk (via GitHub)" <gi...@apache.org>]

git-hulk closed issue #1866: Sonar linter should only take effect on the new code
URL: https://github.com/apache/kvrocks/issues/1866


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@kvrocks.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org