-
Notifications
You must be signed in to change notification settings - Fork 524
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
user docs for bazel coverage usage #1885
Comments
Slipping for the 2.0 release, no reason this can't be done immediately after. |
This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs in two weeks. Collaborators can add a "cleanup" or "need: discussion" label to keep it open indefinitely. Thanks for your contributions to rules_nodejs! |
This issue was automatically closed because it went two weeks without a reply since it was labeled "Can Close?" |
Now that we have easy collection of code coverage whne using
bazel coverage
we should provide users of this with information on how to use the output, in what situations it and how 3rd party rules can contribute coverageThe text was updated successfully, but these errors were encountered: