Kubernetes website and documentation repo:
Go to file
Xiaodong Zhang d4c0ce3a82 Fix invalid link in kubeadm document. (#7870) 2018-04-04 13:13:09 -07:00
.github
_data
_includes Blog Migration: Continuation of WIP PR #7144 (#7247) 2018-04-03 14:19:43 -07:00
_layouts Blog Migration: Continuation of WIP PR #7144 (#7247) 2018-04-03 14:19:43 -07:00
_plugins
_sass
blog Adding CVE Blog Post (#7975) 2018-04-04 12:45:09 -07:00
case-studies
cn
community
css Blog Migration: Continuation of WIP PR #7144 (#7247) 2018-04-03 14:19:43 -07:00
docs Fix invalid link in kubeadm document. (#7870) 2018-04-04 13:13:09 -07:00
images Blog Migration: Continuation of WIP PR #7144 (#7247) 2018-04-03 14:19:43 -07:00
js Blog Migration: Continuation of WIP PR #7144 (#7247) 2018-04-03 14:19:43 -07:00
partners
staging-container
test
update-imported-docs
.gitignore
.travis.yml
404.md
CONTRIBUTING.md
Gemfile Blog Migration: Continuation of WIP PR #7144 (#7247) 2018-04-03 14:19:43 -07:00
Gemfile.lock Blog Migration: Continuation of WIP PR #7144 (#7247) 2018-04-03 14:19:43 -07:00
LICENSE
Makefile Blog Migration: Continuation of WIP PR #7144 (#7247) 2018-04-03 14:19:43 -07:00
OWNERS
OWNERS_ALIASES Remove crassirostris as owner and reviewer (#7974) 2018-04-04 10:22:10 -07:00
README.md
_config.yml Blog Migration: Continuation of WIP PR #7144 (#7247) 2018-04-03 14:19:43 -07:00
_redirects
code-of-conduct.md
editdocs.md
google2b743c61aa37ebbe.html
google3a25d10f6aadcdc0.html
googlea92cf511a27d4f6b.html
googlead862a0628bec321.html
googlebea0044df4aa3179.html
googlece48a67808b497a5.html
index.html
jquery-ui.html
labels.yaml
netlify.toml
netlify_noindex_headers.txt
robots.txt
skip_title_check.txt
skip_toc_check.txt
verify-docs-format.sh

README.md

Instructions for Contributing to the Kubernetes Documentation

Welcome! We are very pleased you want to contribute to the Kubernetes documentation.

You can click the Fork button in the upper-right area of the screen to create a copy of this repository in your GitHub account called a fork. Make any changes you want in your fork, and when you are ready to send those changes to us, go to your fork and create a new pull request to let us know about it.

Once your pull request is created, a Kubernetes reviewer will take responsibility for providing clear, actionable feedback. As the owner of the pull request, it is your responsibility to modify your pull request to address the feedback that has been provided to you by the Kubernetes reviewer. Also note that you may end up having more than one Kubernetes reviewer provide you feedback or you may end up getting feedback from a Kubernetes reviewer that is different than the one originally assigned to provide you feedback. Furthermore, in some cases, one of your reviewers might ask for a technical review from a Kubernetes tech reviewer when needed. Reviewers will do their best to provide feedback in a timely fashion but response time can vary based on circumstances.

For more information about contributing to the Kubernetes documentation, see:

Thank you!

Kubernetes thrives on community participation, and we really appreciate your contributions to our site and our documentation!