docs(site-policy): headings, links, and add Contributor Covenant CODE_OF_CONDUCT.md

Author: TheeNativeHub

CODE_OF_CONDUCT.md

@@ -0,0 +1,80 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address, without their explicit permission
+* Contacting individual members, contributors, or leaders privately, outside designated community mechanisms, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at opensource@github.com. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0, available at <https://www.contributor-covenant.org/version/2/0/code_of_conduct.html>.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at <https://www.contributor-covenant.org/faq>. Translations are available at <https://www.contributor-covenant.org/translations>.

content/site-policy/github-terms/github-community-guidelines.md

@@ -15,28 +15,31 @@ last_updated: 2026-08-18
 
 Millions of developers around the world host projects on GitHub. These guidelines describe what a safe, welcoming, and productive GitHub community looks like and how we expect people to interact on the platform.
 
-Who this applies to
+Scope
+- These guidelines are guidance for contributors, maintainers, and organizations using GitHub.com. They do not replace GitHub's Terms of Service.
+
+## Who this applies to
 - Contributors, maintainers, and organizations using GitHub.
 - Public and private repositories hosted on GitHub.com.
 - Community spaces like issues, pull requests, discussions, and profile pages.
 
-Core principles
+## Core principles
 - Be welcoming and open-minded — welcome newcomers and value diverse perspectives.
 - Be respectful — critique ideas, not people; avoid abusive or demeaning language.
 - Be empathetic — recognize that people come from different backgrounds and experiences.
 - Be constructive — give actionable feedback and write clearly and kindly.
 
-Concrete examples (do / don't)
+## Concrete examples (do / don't)
 - Do: Ask clarifying questions in a code review and provide suggested fixes or references.
 - Don't: Post personal attacks, insults, or slurs directed at a person or group.
-- Do: Create a CONTRIBUTING or CODE_OF_CONDUCT file to set expectations for your repo and link to it from the README.
+- Do: Create a CONTRIBUTING or CODE_OF_CONDUCT file (for example, `/CODE_OF_CONDUCT.md`) to set expectations for your repo and link to it from the README.
 - Don't: Share private information (doxxing) or threats of violence.
 - Do: Use issue templates to request additional information from reporters and to triage bug reports and security concerns.
 - Don't: Repeatedly harass or target a user across multiple issues, PRs, or accounts.
 - Do: Use respectful, technical language when explaining why a change is needed; include examples and steps to reproduce when reporting bugs.
 - Don't: Use sustained trolling behavior, coordinated harassment, or attempts to silence legitimate contributors.
 
-More real-world scenarios
+## More real-world scenarios
 - Hate speech & slurs: Any direct use of slurs, epithets, or language intended to degrade a protected class is not acceptable. Remove or report content that includes these terms used to harass.
 - Doxxing: Posting private or intimate information about someone (home address, phone numbers, non-public social profiles, government ID details) to intimidate or shame is strictly prohibited.
 - Threats & violence: Threats of physical harm, sexual violence, or incitement to violence are disallowed and should be reported immediately.
@@ -45,35 +48,36 @@ More real-world scenarios
 - Targeted harassment campaigns: Coordinated attempts to flood or harass an individual across multiple repos or accounts are prohibited.
 - Abuse of project tools: Using issues, PRs, or comments to continually harass maintainers (for example, by reopening closed discussions, creating duplicate abusive issues) is unacceptable.
 
-Maintainers: tools and best practices
-- Communicate expectations — add CONTRIBUTING and CODE_OF_CONDUCT files and link to them from your README.
+## Maintainers: tools and best practices
+- Communicate expectations — add `CONTRIBUTING` and `CODE_OF_CONDUCT` files and link to them from your README.
 - Moderate comments — users with write access can edit, hide, or remove comments that violate repository rules.
 - Lock conversations — when threads get off-topic, hostile, or repetitive, lock them to stop further comments.
 - Block users — block specific users from interacting with your personal account if needed.
 - Limit interactions — use temporary interaction limits for repos experiencing spam, harassment, or targeted abuse.
 - Use templates — issue and PR templates help gather structured reports and make moderation faster.
 - Create moderation workflows — document how maintainers triage reports, escalate sensitive cases, and communicate actions back to the community.
+- Security: publish a `SECURITY.md` and clearly document how to report security vulnerabilities.
 
-How to report content or behavior
+## How to report content or behavior
 - Use the built-in reporting tools on the offending content (issue, comment, or profile).
 - If you need additional support, contact GitHub Support: {% raw %}{% data variables.contact.contact_support %}{% endraw %} (or replace with https://support.github.com/contact if you prefer an explicit URL).
 - When reporting, include helpful context: direct links to the content, a brief description of why it violates guidelines, and any relevant timestamps or thread links.
 - For legal emergencies or imminent threats to safety, contact local law enforcement in addition to reporting on GitHub.
 
-Enforcement and transparency
+## Enforcement and transparency
 - We rely on community reports and automated detection; each report is reviewed case-by-case by our moderation team.
 - Possible outcomes include removing offending content, limiting visibility, hiding user accounts or organizations from public view, or suspending accounts.
 - We apply a human-centered, proportional approach when responding to reports and aim to provide options for remediation when appropriate.
 - Users may not always receive public details about moderation decisions due to privacy and safety considerations, but we strive for consistent, fair enforcement.
 
-Appeals and reinstatement
-If your content or account is disabled or restricted and you wish to appeal, see the Appeal and Reinstatement page: /site-policy/acceptable-use-policies/github-appeal-and-reinstatement (please verify that the page slug and URL are correct in the site build).
+## Appeals and reinstatement
+If your content or account is disabled or restricted and you wish to appeal, see the Appeal and Reinstatement page: /site-policy/acceptable-use-policies/github-appeal-and-reinstatement (please verify the slug and that the page exists).
 
-Legal notices and license
+## Legal notices and license
 - These Community Guidelines are intended as guidance and do not replace GitHub's Terms of Service.
 - The text of these guidelines is dedicated to the public domain under [CC0-1.0](https://creativecommons.org/publicdomain/zero/1.0/).
 
-Notes for maintainers of this page
+## Notes for maintainers of this page
 - Verify internal variables and shortlinks render correctly in the site build (for example, {% raw %}{% data variables.contact.contact_support %}{% endraw %}).
 - Consider adding localized translations where appropriate.
 - If you prefer an explicit support URL instead of the site variable, replace the contact variable with the canonical support link.