Adds Severity Field for Licenses Violations for Pull Request Scans #672
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
|
I have read the CLA Document and I hereby sign the CLA |
attiasas
added
safe to test
github-actions
bot
removed
the
safe to test
|
Hi @attiasas , |
attiasas
approved these changes
Apr 9, 2024
attiasas
added
bug
github-actions
bot
removed
the
safe to test
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
This PR is to add 'Severity' classification to the License Violations' information, for the Pull Request Scan Results. It is related to the issue: #666, as it helps with resolving one aspects discussed in that issue, which is for PR Scans.
This functionality is helpful to differentiate among the levels of violations, for developers to act on, while working on PRs.
It adds the column for 'Severity' as shown in the below screenshot:
This image has been added in the change, to update it as it is referenced in the documentation.