Open
Conversation
This file contains hidden or 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
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.
Hello 👋 from the VA GitHub.com team!
We are requesting via this Pull request that you enable Advanced Security Code Scanning. Advanced Security Code Scanning is a feature on GitHub that the VA is already paying for, and we kindly request that you utilize it to improve your repository's security. This is a compliment to any tools and security procedures your team is already performing rather than a replacement. We are excited to get this enabled as it gets developers information about the security of the code early, before it's even merged in.
This pull request will attempt an automatic scan for security vulnerabilities in the code of this repository. If there is a build failure or results that you would like assistance with, we would be happy to work with you. You can schedule here or reach us at va-delivery@github.com.
Once merged, this feature will identify potential security issues on any new pull requests. These should be reviewed with any security folks on your team. For more information, check out the GitHub Handbook. A great place to start if you have a lot of potential vulnerabilities is to address new vulnerabilities only for a period of time and then scheduling time to regularly reduce the backlog of potential vulnerabilities. This will minimize negative impact to current release schedules and productivity.
With all that being said, please consider merging this once the checks pass. Thank you and happy coding!