From 2c31d6a19d87f1d628529f1301ed51b6af3b0e86 Mon Sep 17 00:00:00 2001 From: Anna Jung Date: Fri, 9 Oct 2020 15:11:27 -0500 Subject: [PATCH] Update new feature doc to add a step to include necessary links --- .github/PULL_REQUEST_TEMPLATE.md | 7 +++---- content/en/docs/contribute/new-content/new-features.md | 3 ++- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md index 41147a8225..785257142d 100644 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -14,12 +14,11 @@ Use the default base branch, “master”, if you're documenting existing features in the English localization. - If you're working on a different localization (not English), or you - are documenting a feature that will be part of a future release, see + If you're working on a different localization (not English), see https://kubernetes.io/docs/contribute/new-content/overview/#choose-which-git-branch-to-use for advice. - Use the next release branch, "dev-x.xx", if you're documenting a feature for - a release. If applicable, please also include links to k/k and k/enhancement. + If you're documenting a feature that will be part of a future release, see + https://kubernetes.io/docs/contribute/new-content/new-features/ for advice. --> diff --git a/content/en/docs/contribute/new-content/new-features.md b/content/en/docs/contribute/new-content/new-features.md index 54db84da8f..98823185ff 100644 --- a/content/en/docs/contribute/new-content/new-features.md +++ b/content/en/docs/contribute/new-content/new-features.md @@ -98,7 +98,8 @@ deadlines. 1. Open a pull request against the `dev-{{< skew nextMinorVersion >}}` branch in the `kubernetes/website` repository, with a small 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 this release that the feature docs are coming.