Skip to content

Conversation

@GitHub-Creeper
Copy link

1 commit being made: "In the "What is Not Allowed?" section, "Anyone under the age of 13", despite the trade-off being less concise, I made the rules more emotional. Also, added "diverse" to the Pledge section."

Why:

There was room to improve the tone of the Code of Conduct in the “What is Not Allowed?” section. The original phrasing was legally correct but emotionally flat. This update introduces a more empathetic, human-centered explanation regarding age restrictions while maintaining compliance. Additionally, I added the word “diverse” to the Pledge to better reflect inclusive values. I know that GitHub tries to be as emotional as possible, but this is 1 minor improvement.

Closes: No related issue — this is a minor tone and clarity improvement.

What's being changed (if available, include any code snippets, screenshots, or gifs):

  • Rewrote the paragraph about users under 13 to sound more compassionate and encouraging, not just procedural.
  • Clarified that exceptions cannot be made due to legal reasons.
  • Added “diverse” to the community pledge to enhance inclusivity messaging.

No structural or functional documentation changes were made; this PR is purely tone-focused.

Check off the following:

  • A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
  • The changes in this PR meet the docs fundamentals that are required for all content.
  • All CI checks are passing and the changes look good in the review environment.

In the "What is Not Allowed?" section, "Anyone under the age of 13", despite the trade-off being less concise, made the rules more emotional. Also, added "diverse" to the Pledge section.
@GitHub-Creeper GitHub-Creeper requested a review from a team as a code owner July 8, 2025 03:03
@welcome
Copy link

welcome bot commented Jul 8, 2025

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.

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Jul 8, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Jul 8, 2025

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source Review Production What Changed
site-policy/github-terms/github-community-code-of-conduct.md fpt
fpt

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

@Cdeangelogmhs08

This comment was marked as spam.

@Sharra-writes
Copy link
Contributor

@GitHub-Creeper Thanks for opening a PR! Unfortunately the site policy docs go through our legal team, not our docs team. They can be dry, yes, but that's usually for legal reasons. We basically aren't allowed to touch them except for typo fixes. If you'd like to contribute, we do have a handy help wanted label over in issues for stuff we would like help with. This would be an especially good first PR because a subject matter expert gave me the exact wording we should use in that comment I linked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

triage Do not begin working on this issue until triaged by the team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants