The open-source repo for docs.github.com
Перейти к файлу
Christos Nikolaou 486af71b14
Fix quote char on "Planning your migration to GH" (#30080)
2023-11-20 18:01:19 +00:00
.devcontainer Remove codespace auto-preview from devcontainer.json 2023-10-17 09:54:44 +01:00
.github ignore node updates (#46295) 2023-11-17 19:31:33 +00:00
.vscode
assets Update markdown alert section (#45922) 2023-11-16 22:48:43 +00:00
content Fix quote char on "Planning your migration to GH" (#30080) 2023-11-20 18:01:19 +00:00
contributing Deprecate `contributing` directory (#45581) 2023-11-13 17:55:50 +00:00
data GraphQL schema update (#46344) 2023-11-18 16:34:25 +00:00
src Update audit log event data (#46445) 2023-11-20 16:33:40 +00:00
.dockerignore Move files out of script/ (#45454) 2023-11-02 18:17:39 +00:00
.editorconfig
.env.example
.gitattributes
.gitignore Let's find out if next-env.d.ts is ignorable (#45765) 2023-11-13 17:06:00 +00:00
.npmrc Next 13.4 and React 18 (#40039) 2023-08-09 14:30:26 +00:00
.prettierignore Move files out of script/ (#45454) 2023-11-02 18:17:39 +00:00
Dockerfile Move components into src/frame (#45759) 2023-11-13 17:18:51 +00:00
Dockerfile.openapi_decorator Update Dockerfile.openapi_decorator (#46133) 2023-11-14 18:29:12 +00:00
LICENSE
LICENSE-CODE Update MIT License year from `2022` -> `2023` (#25557) 2023-05-22 17:20:55 +00:00
README.md Update README.md (#40598) 2023-10-02 14:44:22 +00:00
docker-compose.yaml
next.config.js Move files out of lib/ (#45506) 2023-11-02 22:46:32 +00:00
package-lock.json Bump next from 13.5.6 to 14.0.2 (#46148) 2023-11-20 17:30:44 +00:00
package.json Bump next from 13.5.6 to 14.0.2 (#46148) 2023-11-20 17:30:44 +00:00
tsconfig.json

README.md

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.

Use the table of contents icon on the top left corner of this document to navigate to a specific section quickly.

Contributing

We accept different types of contributions, including some that don't require you to write a single line of code. For detailed instructions on how to get started with our project, see "About contributing to GitHub Docs."

Ways to contribute

On the GitHub Docs site, you can contribute by clicking the Make a contribution button at the bottom of the page to open a pull request for quick fixes like typos, updates, or link fixes.

You can also contribute by creating a local environment or opening a Codespace. For more information, see "Setting up your environment to work on GitHub Docs."

For more complex contributions, please open an issue using the most appropriate issue template to describe the changes you'd like to see.

If you're looking for a way to contribute, you can scan through our help wanted board to find open issues already approved for work.

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 the discussions.

And that's it!

If you're having trouble with your GitHub account, contact Support.

That's how you can easily become a member of the GitHub Docs community.

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:

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 the MIT license.

When using the GitHub logos, be sure to follow the GitHub logo guidelines.

Thanks 💜

Thanks for all your contributions and efforts towards improving the GitHub documentation. We thank you for being part of our community !