We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
One of the greatest advantages of Wallaby is its code coverage. No else tool on the market collects information in a similar depth and quality.
Unfortunately, this information is available only for the change author and cannot be seen during the PR phase or at health dashboards.
Wondering if is it possible to detach this plugin from Wallaby core and execute it at CI to generate coverage reports one can use in external systems.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Issue description or question
One of the greatest advantages of Wallaby is its code coverage. No else tool on the market collects information in a similar depth and quality.
Unfortunately, this information is available only for the change author and cannot be seen during the PR phase or at health dashboards.
Wondering if is it possible to detach this plugin from Wallaby core and execute it at CI to generate coverage reports one can use in external systems.
The text was updated successfully, but these errors were encountered: