kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update new feature doc to add a step to include necessary links

This commit is contained in:
Anna Jung 2020-10-09 15:11:27 -05:00
parent 91ae1f7e19
commit 2c31d6a19d
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
.github/PULL_REQUEST_TEMPLATE.md vendored
View File

@ -14,12 +14,11 @@
Use the default base branch, “master”, if you're documenting existing Use the default base branch, “master”, if you're documenting existing
features in the English localization. features in the English localization.
If you're working on a different localization (not English), or you If you're working on a different localization (not English), see
are documenting a feature that will be part of a future release, see
https://kubernetes.io/docs/contribute/new-content/overview/#choose-which-git-branch-to-use https://kubernetes.io/docs/contribute/new-content/overview/#choose-which-git-branch-to-use
for advice. for advice.
Use the next release branch, "dev-x.xx", if you're documenting a feature for If you're documenting a feature that will be part of a future release, see
a release. If applicable, please also include links to k/k and k/enhancement. https://kubernetes.io/docs/contribute/new-content/new-features/ for advice.
--> -->

3
content/en/docs/contribute/new-content/new-features.md
View File

@ -98,7 +98,8 @@ deadlines.
1. Open a pull request against the 1. Open a pull request against the
`dev-{{< skew nextMinorVersion >}}` branch in the `kubernetes/website` repository, with a small `dev-{{< skew nextMinorVersion >}}` branch in the `kubernetes/website` repository, with a small
commit that you will amend later. commit that you will amend later.
2. Use the Prow command `/milestone {{< skew nextMinorVersion >}}` to 2. Edit the pull request description to include links to `k/k` PR(s) and `k/enhancement` issue(s).
3. Use the Prow command `/milestone {{< skew nextMinorVersion >}}` to
assign the PR to the relevant milestone. This alerts the docs person managing assign the PR to the relevant milestone. This alerts the docs person managing
this release that the feature docs are coming. this release that the feature docs are coming.