Skip to content
Browse files

Adding contribution best practice in contribute docs (#18059)

  • Loading branch information
vishakhanihore committed Feb 8, 2020
1 parent 700ac79 commit 4c3a5c6f5f0b262b00c228eafe47d6eaaca0a907
Showing with 11 additions and 0 deletions.
  1. +11 −0 content/en/docs/contribute/
@@ -34,6 +34,17 @@ To get involved with documentation:
2. Familiarize yourself with the [documentation repository]( and the website's [static site generator](
3. Make sure you understand the basic processes for [improving content]( and [reviewing changes](

## Contributions best practices

- Do write clear and meaningful GIT commit messages.
- Make sure to include _Github Special Keywords_ which references the issue and automatically closes the issue when PR is merged.
- When you make a small change to a PR like fixing a typo, any style change, or changing grammar. Make sure you squash your commits so that you dont get a large number of commits for a relatively small change.
- Make sure you include a nice PR description depicting the code you have changes, why to change a following piece of code and ensuring there is sufficient information for the reviewer to understand your PR.
- Additional Readings :
- [](
- [ ]( )
- [ ]( )

## Other ways to contribute

- To contribute to the Kubernetes community through online forums like Twitter or Stack Overflow, or learn about local meetups and Kubernetes events, visit the [Kubernetes community site](/community/).

0 comments on commit 4c3a5c6

Please sign in to comment.
You can’t perform that action at this time.