Reword security contact description for clarity #1633
Merged
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
This doesn't change the contact, just rewords it to avoid possible future ambiguity, now that the repository is in an org. See GitoxideLabs#1632.
4 tasks
Member
|
Thanks a lot, this works perfectly! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Closes #1632
This doesn't change the contact, just rewords it to avoid possible future ambiguity, now that the repository is in an org.
This is one of several possible wording changes that I think could be done in accordance with #1632 (comment). Another possibility could be to keep all the previous wording and just replace "my". I'd be pleased to make adjustments to this PR and also I of course do not mind if you make them.
It's just occurred to me that I don't know if changes apply only to
SECURITY.mdshould have adoc:prefix in the commit message title. I think they don't need one but I'm not sure.