whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #35120 from fenggw-fnst/fix-open-a-pr

Browse Source 
Fix indentation and clean up in open-a-pr.md
This commit is contained in:
Kubernetes Prow Robot
2022-07-18 01:55:15 -07:00
committed by GitHub
parent ff2fbee6f7 525a952b95
commit b8e27e7382
1 changed files with 10 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/contribute/new-content/open-a-pr.md
+10 -10
View File
@@ -216,16 +216,16 @@ Figure 2. Working from a local fork to make your changes.
1. Decide which branch base to your work on: 1. Decide which branch base to your work on:
- For improvements to existing content, use `upstream/main`. - For improvements to existing content, use `upstream/main`.
- For new content about existing features, use `upstream/main`. - For new content about existing features, use `upstream/main`.
- For localized content, use the localization's conventions. For more information, see - For localized content, use the localization's conventions. For more information, see
[localizing Kubernetes documentation](/docs/contribute/localization/). [localizing Kubernetes documentation](/docs/contribute/localization/).
- For new features in an upcoming Kubernetes release, use the feature branch. For more - For new features in an upcoming Kubernetes release, use the feature branch. For more
information, see [documenting for a release](/docs/contribute/new-content/new-features/). information, see [documenting for a release](/docs/contribute/new-content/new-features/).
- For long-running efforts that multiple SIG Docs contributors collaborate on, - For long-running efforts that multiple SIG Docs contributors collaborate on,
like content reorganization, use a specific feature branch created for that effort. like content reorganization, use a specific feature branch created for that effort.
If you need help choosing a branch, ask in the `#sig-docs` Slack channel. If you need help choosing a branch, ask in the `#sig-docs` Slack channel.
1. Create a new branch based on the branch identified in step 1. This example assumes the base 1. Create a new branch based on the branch identified in step 1. This example assumes the base
branch is `upstream/main`: branch is `upstream/main`:
@@ -234,7 +234,7 @@ Figure 2. Working from a local fork to make your changes.
git checkout -b <my_new_branch> upstream/main git checkout -b <my_new_branch> upstream/main
``` ```
3. Make your changes using a text editor. 1. Make your changes using a text editor.
At any time, use the `git status` command to see what files you've changed. At any time, use the `git status` command to see what files you've changed.