New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SLCORE-766 Analysis in SLOOP - Local tracking #959
Conversation
5ab0f76
to
7125c00
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While implementing the set focus on new code in standalone mode, I noticed some parts to be improved. I added some comments regarding them
backend/core/src/main/java/org/sonarsource/sonarlint/core/tracking/IssueMatchingService.java
Show resolved
Hide resolved
backend/core/src/main/java/org/sonarsource/sonarlint/core/tracking/IssueMatchingService.java
Outdated
Show resolved
Hide resolved
backend/core/src/main/java/org/sonarsource/sonarlint/core/tracking/IssueMatchingService.java
Show resolved
Hide resolved
* Add medium tests for issue tracking * SLCORE-777 Perform issue tracking before raising issue --------- Co-authored-by: Damien Urruty <damien.urruty@sonarsource.com>
* API changes documentation, improved deprecations, some tests --------- Co-authored-by: Damien Urruty <damien.urruty@sonarsource.com>
…pecific lines in a file
* SLCORE-768 provide git blaming with base dir path * SLCORE-768 set IntroductionDate for new issues * SLCORE-773 set newCode true for unmatched local issues in connected mode * SLCORE-768 add medium tests for setting introduction date and new code * SLCORE-768 Minor review refactoring --------- Co-authored-by: Vojtech Suchy <vojtech.suchy@sonarsource.com>
e900edd
to
acba071
Compare
Quality Gate passedIssues Measures |
No description provided.