-
Notifications
You must be signed in to change notification settings - Fork 59.2k
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
Update github-community-guidelines.md #34346
Conversation
Emphasized key points
Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
Automatically generated comment ℹ️This comment is automatically generated and will be overwritten every time changes are committed to this branch. The table contains an overview of files in the Content directory changesYou may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.
fpt: Free, Pro, Team |
@Pcharlesme Thank you for opening a PR! ✨
Can you expand on why you made these updates, and what you feel they add to this doc? 💛 |
@nguyenalex836 Thank you What it adds: By using straightforward terms like "We prioritize" instead of "We optimize for," it reduces cognitive load |
@Pcharlesme Thank you for your elaboration! I'll get this triaged for review ✨ |
@Pcharlesme Thank you for your patience! After discussion, our team determined you will need to open a contribution within the Site Policy repository, as their team will need to approve your PR 💛 I'll go ahead and close this issue. Thank you for your desire to contribute to our docs! |
Emphasized key points
Why:
Closes:
What's being changed (if available, include any code snippets, screenshots, or gifs):
Check off the following:
I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).
data
directory.For content changes, I have completed the self-review checklist.