bf2cf84e94
* Update github-acceptable-use-policies.md * Update github-community-guidelines.md * tweaks to appeal and reinstatement section * Update github-community-guidelines.md tweaks to malware section per seclab team * Update content/github/site-policy/github-community-guidelines.md Co-authored-by: Bas Alberts <13686387+anticomputer@users.noreply.github.com> * Update github-community-guidelines.md * Update github-community-guidelines.md * Update github-community-guidelines.md made Tyler's suggestion re: GitHub `supports` * Update content/github/site-policy/github-community-guidelines.md * remove trailing spaces * AUP/CG community feedback iteration #1 Based on your feedback so far, we propose the following iteration on our language, we look forward to your continued participation and suggestions. Specifically we attempted to address your feedback in the following areas: - clarify and narrow terms such as "harm" and "harmful" - remove any disclosure methodology bias - clarify intent of incident response driven restrictions, how those restrictions occur, and what restrictions would look like - provide clearer examples of what is and what is not allowed - clarify that dual use software is welcome by default and that incident response is tied to specific instances of platform abuse, not code contents or code copies - clarify intent of security contact recommendation, add flexibility to alleviate PII concerns * Apply suggestions from code review Co-authored-by: Abby Vollmer <vollmera@users.noreply.github.com> * unreorder * Add link to CG from content restrictions * fragment * confirmed with the Docs team that this is the current format for relative links in Docs * consistent indentation * correct indentation * consistent source indentation even * Update content/github/site-policy/github-community-guidelines.md Co-authored-by: Bas Alberts <13686387+anticomputer@users.noreply.github.com> * Update content/github/site-policy/github-acceptable-use-policies.md Co-authored-by: Bas Alberts <13686387+anticomputer@users.noreply.github.com> * Update content/github/site-policy/github-community-guidelines.md Co-authored-by: Bas Alberts <13686387+anticomputer@users.noreply.github.com> * Update github-acceptable-use-policies.md * Update github-community-guidelines.md * Update content/github/site-policy/github-community-guidelines.md Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> * Update github-community-guidelines.md * Update github-acceptable-use-policies.md * Update content/github/site-policy/github-acceptable-use-policies.md Co-authored-by: Laura Coursen <lecoursen@github.com> Co-authored-by: Abby Vollmer <vollmera@users.noreply.github.com> Co-authored-by: Bas Alberts <13686387+anticomputer@users.noreply.github.com> Co-authored-by: Mike Linksvayer <mlinksva@github.com> Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> Co-authored-by: Laura Coursen <lecoursen@github.com> Co-authored-by: Melanie Yarbrough <11952755+myarb@users.noreply.github.com>
GitHub Docs
This repository contains the documentation website code and Markdown source files for docs.github.com.
GitHub's Docs team works on pre-production content in a private repo that regularly syncs with this public repo.
In this article:
Contributing
Start contributing right now:
We accept a lot of different contributions, including some that don't require you to write a single line of code.
Click make a contribution from docs
As you're using GitHub Docs, you may find something in an article that you'd like to add to, update, or change. Click on make a contribution to navigate directly to that article in the codebase, so that you can begin making your contribution.
Open an issue
If you've found a problem, you can open an issue using a template.
Solve an issue
If you have a solution to one of the open issues, you will need to fork the repository and submit a pull request using the template that is visible automatically in the pull request body. For more details about this process, please check out Getting Started with Contributing.
Join us in discussions
We use GitHub Discussions to talk about all sorts of topics related to documentation and this site. For example: if you'd like help troubleshooting a PR, have a great new idea, or want to share something amazing you've learned in our docs, join us in discussions.
And that's it!
That's how you can get started easily as a member of the GitHub Documentation community. ✨
If you want to know more, or you're making a more complex contribution, check out Getting Started with Contributing.
There are a few more things to know when you're getting started with this repo:
- If you're having trouble with your GitHub account, contact Support.
- We do not accept pull requests for translated content - see CONTRIBUTING.md for more information.
READMEs
In addition to the README you're reading right now, this repo includes other READMEs that describe the purpose of each subdirectory in more detail:
- content/README.md
- content/graphql/README.md
- content/rest/README.md
- contributing/README.md
- data/README.md
- data/reusables/README.md
- data/variables/README.md
- includes/liquid-tags/README.md
- includes/README.md
- javascripts/README.md
- layouts/README.md
- lib/liquid-tags/README.md
- middleware/README.md
- script/README.md
- stylesheets/README.md
- tests/README.md
License
The GitHub product documentation in the assets, content, and data folders are licensed under a CC-BY license.
All other code in this repository is licensed under a MIT license.
When using the GitHub logos, be sure to follow the GitHub logo guidelines.