92d5722103
* Add 2.22.0 * Add 2.22.1 * Add 2.22.2 * Add 2.22.3 * Add 2.22.4 * Lint YAML files * intro shouldn't be required * Align all notes * Full height sidebar * Make the sidebar full height properly * Get the real layout going * Include full name * Move details > summary around * Fix sticky sidebar * Tweak bottom of page * Add more label colors * Change heading title * Don't be <details>, change sticky header * Include other releases' info * Show prev/next links * Change sidenav to show all releases * Fix ordering of chevron * Fix link underlines * Collapsing minor versions * Moar padding * Setup schema for sub-sections * Update a YAML file to match schema * Redo rendering/sorting logic * Update layout * Convert remaining notes * Improve schema * Use proper min properties * Custom bullet points * Show details control for version picker * Improve layout on small screens * One more tiny fix * Order by semver * Use proper version in details * Fix extra arrows showing up * Change label colors * Pass the reference check * Add gradients * Gradient all the things
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 the 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.