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

APPSECTOOLS-25695 Sec Onboard: Repo Contact Info #24

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

svc-rat-appsec
Copy link

🚨 🚨 🚨 🚨 🚨 🚨 🚨 🚨 🚨 🚨 🚨 🚨 🚨 🚨
.
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 CHANGEME with 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?

  • Adds a .security_config/security_contact.yaml template to your repo

What do I need to do?

Please merge this pull request and update the CHANGEME fields in the
file 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_config folder under
the 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.

@svc-rat-appsec svc-rat-appsec force-pushed the feature/APPSECTOOLS-25695-sec-onboard-repo-contact-info branch 4 times, most recently from defbf45 to 7805f9c Compare July 7, 2024 05:16
@svc-rat-appsec svc-rat-appsec force-pushed the feature/APPSECTOOLS-25695-sec-onboard-repo-contact-info branch 3 times, most recently from ef97885 to 85a6884 Compare July 19, 2024 05:49
@svc-rat-appsec svc-rat-appsec force-pushed the feature/APPSECTOOLS-25695-sec-onboard-repo-contact-info branch 2 times, most recently from 7e64964 to 3b2bb82 Compare July 28, 2024 04:55
@svc-rat-appsec svc-rat-appsec force-pushed the feature/APPSECTOOLS-25695-sec-onboard-repo-contact-info branch 2 times, most recently from 1e64229 to 737a468 Compare August 18, 2024 04:53
@svc-rat-appsec svc-rat-appsec force-pushed the feature/APPSECTOOLS-25695-sec-onboard-repo-contact-info branch 2 times, most recently from d2247bf to 4d63490 Compare September 1, 2024 04:55
@svc-rat-appsec svc-rat-appsec force-pushed the feature/APPSECTOOLS-25695-sec-onboard-repo-contact-info branch from 4d63490 to 9b6c03e Compare September 9, 2024 04:42
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.

1 participant