DEMO: Replace SECURITY_CONTACTS file with security_contacts in OWNERS #2
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
sfowl
force-pushed
the
example-owners-update
branch
from
d8bfc55
to
866829e
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.
This is example PR showing the proposed changes to security contact information (see #56), in this example, the component is
client-go.security_contacts(with subkeysgithub,emailandslack)security_contactsapprovershave also been added tosecurity_contactsEmail addresses from public github profiles have also been included forsecurity_contacts, some minor obfuscation has been appliedIf this example is works, I can proceed with opening similar PRs against the entire kubernetes organization.