-
Notifications
You must be signed in to change notification settings - Fork 3
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
Move comments creation to the model #288
Conversation
🎓 Quality Checks - 328 of 400🚦 JUnit - 100 of 10071 tests passed 🐾 JaCoCo - 76 of 10076% Covered , 24% Missed 🦠 PIT - 72 of 10072% Killed , 28% Survived
|
🎓 Quality Checks - 327 of 400🚦 JUnit - 100 of 10071 tests passed 🐾 JaCoCo - 75 of 10075% Covered , 25% Missed 🦠 PIT - 72 of 10072% Killed , 28% Survived
|
🎓 Quality Checks - 330 of 400🚦 JUnit - 100 of 10071 tests passed 🐾 JaCoCo - 75 of 10075% Covered , 25% Missed 🦠 PIT - 72 of 10072% Killed , 28% Survived
|
🎓 Quality Checks - 339 of 400🚦 JUnit - 100 of 10071 tests passed 🐾 JaCoCo - 75 of 10075% Covered , 25% Missed 🦠 PIT - 72 of 10072% Killed , 28% Survived
|
Comments for static analysis warnings, for lines with missing coverage, and for lines with survived mutations can be rendered in GitHub and GitLab using different APIs. The base class that creates the comments is now part of the model while the implementations that use the vendor specific API are placed in the corresponding actions.