APPSECTOOLS-25695 Sec Onboard: Repo Contact Info #24
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
svc-rat-appsec
force-pushed
the
feature/APPSECTOOLS-25695-sec-onboard-repo-contact-info
branch
4 times, most recently
from
defbf45
to
7805f9c
Compare
svc-rat-appsec
force-pushed
the
feature/APPSECTOOLS-25695-sec-onboard-repo-contact-info
branch
3 times, most recently
from
ef97885
to
85a6884
Compare
svc-rat-appsec
force-pushed
the
feature/APPSECTOOLS-25695-sec-onboard-repo-contact-info
branch
2 times, most recently
from
7e64964
to
3b2bb82
Compare
svc-rat-appsec
force-pushed
the
feature/APPSECTOOLS-25695-sec-onboard-repo-contact-info
branch
2 times, most recently
from
1e64229
to
737a468
Compare
svc-rat-appsec
force-pushed
the
feature/APPSECTOOLS-25695-sec-onboard-repo-contact-info
branch
2 times, most recently
from
d2247bf
to
4d63490
Compare
svc-rat-appsec
force-pushed
the
feature/APPSECTOOLS-25695-sec-onboard-repo-contact-info
branch
from
4d63490
to
9b6c03e
Compare
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.
🚨 🚨 🚨 🚨 🚨 🚨 🚨 🚨 🚨 🚨 🚨 🚨 🚨 🚨
.
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_cybersecurity.