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

Reword security contact description for clarity #1633

Merged
merged 1 commit into from
Oct 16, 2024

Conversation

EliahKagan
Copy link
Member

@EliahKagan EliahKagan commented Oct 16, 2024

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.md should have a doc: prefix in the commit message title. I think they don't need one but I'm not sure.

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.
@Byron
Copy link
Member

Byron commented Oct 16, 2024

Thanks a lot, this works perfectly!

@Byron Byron merged commit c081114 into GitoxideLabs:main Oct 16, 2024
15 checks passed
@EliahKagan EliahKagan deleted the contact-wording branch October 16, 2024 06:58
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.

GitoxideLabs-related updates other than URLs in this repo
2 participants