compare-coverage-to-main
Advanced tools
Compares the current json coverage file to that of the latest release
Compares the current json coverage file to that of the latest release and provides a comment on pull requests with that information.
coverage-summary.json (Must be from the json-summary coverage reporter in istanbul)--coverage flag.compare-coverage-to-main - Tool to compare coverage for a PR with the main branch
usage: compare-coverage-to-main -f <path to coverage file> -o <org> -r <repo> -p <pull request id>
options:
-h, --help show help and usage
-v, --version show version
-f, --coverage-filepath <path> path to new coverage summary
-d, --dry-run if true, does not post comment to PR
-o, --owner <string> the repository owner
-p, --pr-id <number> the PR id
-r, --repo <repository name> the repository name
FAQs
Compares the current json coverage file to that of the latest release
We found that compare-coverage-to-main demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.