APPSECTOOLS-15464 Sec Onboard: Repo Contact Info #10
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.
🚨 🚨 🚨 🚨 🚨 🚨 🚨 🚨 🚨 🚨 🚨 🚨 🚨 🚨
.
The Pull Request Approver MUST ALSO MERGE THIS PULL REQUEST
.
🚨 🚨 🚨 🚨 🚨 🚨 🚨 🚨 🚨 🚨 🚨 🚨 🚨 🚨
.
.
Sec Onboard - Repo Contact Info - Pull Request
.
ℹ️ Please Review, Update, & Merge this Pull request
ℹ️ Replace all values of
CHANGEMEwith the appropriate values..
Code Repo Contact Information
In order to ensure we can quickly identify and contact the owners of a
repo when security issues are found in their code, we need teams to
populate a standardized ownership and contact metadata file in each
repo they control. This pull request provides a template for such a
file. Our ask to teams is to merge and update it to reflect the
appropriate contact info for your team.
.
For additional details, please see go/repocontact
.
What changes does this Pull Request make?
.security_config/security_contact.yamltemplate to your repoWhat do I need to do?
Please merge this pull request and update the
CHANGEMEfields in thefile to the appropriate values for your team.
If this is a monorepo where different parts of the repo have different owners,
you may duplicate and relocate this file to a
.security_configfolder underthe root of each subproject contained in this repo.
If you have additional questions about the format, please view the FAQ at go/repocontact or ask in #ask_cybersecurity30.