diff options
| author | Christian Simon <simon@swine.de> | 2018-12-07 17:30:46 +0000 |
|---|---|---|
| committer | Stephen Augustus <saugustus@vmware.com> | 2019-01-19 11:19:09 -0500 |
| commit | 6152d6a57ea89b252e94fc7a55ba71ddc747d784 (patch) | |
| tree | 818fb7a4f6e9285ea0a00b504d1d1fa1efcf0061 | |
| parent | 8a602db69783ce37d5d3d8d82f9c2c7895fc0f50 (diff) | |
Fix cherry-pick link
| -rw-r--r-- | contributors/guide/release-notes.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/guide/release-notes.md b/contributors/guide/release-notes.md index 926f5946..655dff1c 100644 --- a/contributors/guide/release-notes.md +++ b/contributors/guide/release-notes.md @@ -30,4 +30,4 @@ For pull requests that don't need to be mentioned at release time, use the `/rel To see how to format your release notes, view the kubernetes/kubernetes [pull request template](https://git.k8s.io/kubernetes/.github/PULL_REQUEST_TEMPLATE.md) for a brief example. Pull Request titles and body comments can be modified at any time prior to the release to make them friendly for release notes. -Release notes apply to pull requests on the master branch. For cherry-pick pull requests, see the [cherry-pick instructions](contributors/devel/cherry-picks.md). The only exception to these rules is when a pull request is not a cherry-pick and is targeted directly to the non-master branch. In this case, a `release-note-*` label is required for that non-master pull request. +Release notes apply to pull requests on the master branch. For cherry-pick pull requests, see the [cherry-pick instructions](/contributors/devel/cherry-picks.md). The only exception to these rules is when a pull request is not a cherry-pick and is targeted directly to the non-master branch. In this case, a `release-note-*` label is required for that non-master pull request. |