Skip to content
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

Configure WhiteSource for GitHub.com #202

Open
wants to merge 1 commit into
base: snappy/branch-2.1
Choose a base branch
from

Conversation

mend-for-github-com[bot]
Copy link

Welcome to WhiteSource for GitHub.com! This is an onboarding PR to help you understand and configure settings before WhiteSource starts scanning your repository for security vulnerabilities.

🚦 WhiteSource for GitHub.com will start scanning your repository only once you merge this Pull Request. To disable WhiteSource 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, WhiteSource for GitHub.com will use the default configuration.

Before merging this PR, Make sure the Issues tab is enabled. Once you merge this PR, WhiteSource 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 WhiteSource Remediate Workflow Rules are set on your repository (from the WhiteSource 'Integrate' tab), WhiteSource will also generate a fix Pull Request for relevant vulnerabilities.


❓ Got questions? Check out WhiteSource for GitHub.com docs.
If you need any further assistance then you can also request help here.

@sumwale sumwale force-pushed the snappy/branch-2.1 branch 4 times, most recently from 4ffe404 to 79ddd88 Compare June 13, 2021 14:16
@sumwale sumwale force-pushed the snappy/branch-2.1 branch 2 times, most recently from 52a9a47 to 763e1bb Compare June 17, 2021 15:26
@sumwale sumwale force-pushed the snappy/branch-2.1 branch 5 times, most recently from 1456d1f to 3d73189 Compare June 27, 2021 18:39
@sumwale sumwale force-pushed the snappy/branch-2.1 branch 6 times, most recently from 1feaa36 to cdd6d29 Compare April 6, 2022 23:24
@sumwale sumwale force-pushed the snappy/branch-2.1 branch 3 times, most recently from cba053b to 3527357 Compare June 10, 2022 08:59
@sumwale sumwale force-pushed the snappy/branch-2.1 branch from 0169c3d to 1fb3673 Compare June 12, 2022 12:56
@sumwale sumwale force-pushed the snappy/branch-2.1 branch from 4a3161a to efa4458 Compare June 29, 2022 09:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants