Update Line 2

The title just said Continuous Integration whereas the blurb below says Continuous Integration and Continuous Deployment.
1 file changed
tree: 042ee7ca1ee26ec9aaf70779fb423db6f348b00e
  1. .github/
  2. .vscode/
  3. assets/
  4. content/
  5. contributing/
  6. data/
  7. docs/
  8. includes/
  9. javascripts/
  10. layouts/
  11. lib/
  12. middleware/
  13. react/
  14. script/
  15. stylesheets/
  16. tests/
  17. translations/
  18. .devcontainer.json
  19. .editorconfig
  20. .env.example
  21. .eslintignore
  22. .eslintrc.js
  23. .gitattributes
  24. .gitignore
  25. .node-version
  26. .npmrc
  27. .pa11yci
  28. .prettierignore
  29. .prettierrc.json
  30. app.json
  33. crowdin.yml
  34. docker-compose.yaml
  35. Dockerfile
  36. Dockerfile.openapi_decorator
  37. feature-flags.json
  38. Gemfile
  39. Gemfile.lock
  40. jest-puppeteer.config.js
  41. jest.config.js
  44. nodemon.json
  45. ownership.yaml
  46. package-lock.json
  47. package.json
  48. Procfile
  49. README.md
  50. server.js
  51. webpack.config.js

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:


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. :sparkles:

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:

  1. If you're having trouble with your GitHub account, contact Support.
  2. We do not accept pull requests for translated content - see CONTRIBUTING.md for more information.


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:


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.