Closed mend-for-github-com[bot] closed 2 months ago
Merging #285 (8773f89) into main (a8b0716) will not change coverage. The diff coverage is
n/a
.
@@ Coverage Diff @@
## main #285 +/- ##
=======================================
Coverage 97.33% 97.33%
=======================================
Files 25 25
Lines 1090 1090
=======================================
Hits 1061 1061
Misses 29 29
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more
Closing as already using Mend
Welcome to Mend for GitHub.com (formerly WhiteSource). This is an onboarding PR to help you understand and configure settings before Mend starts scanning your repository for security vulnerabilities.
:vertical_traffic_light: Mend for GitHub.com will start scanning your repository only once you merge this Pull Request. To disable Mend for GitHub.com, simply close this Pull Request.
What to Expect
This PR contains a '.whitesource' configuration file which can be customized to your needs. If no changes were applied to this file, Mend for GitHub.com will use the default configuration.
Before merging this PR, Make sure the Issues tab is enabled. Once you merge this PR, Mend for GitHub.com will scan your repository and create a GitHub Issue for every vulnerability detected in your repository.
If you do not want a GitHub Issue to be created for each detected vulnerability, you can edit the '.whitesource' file and set the 'minSeverityLevel' parameter to 'NONE'.
If Mend Remediate Workflow Rules are set on your repository (from the Mend 'Integrate' tab), Mend will also generate a fix Pull Request for relevant vulnerabilities.
:question: Got questions? Check out Mend for GitHub.com docs. If you need any further assistance then you can also request help here.