Update code standards to direct folks to create changelogs on release… (#4443)

* Update code standards to direct folks to create changelogs on release branches
* Fix wording

Signed-off-by: Abigail McCarthy <mabigail@vmware.com>
pull/4461/head
Abigail McCarthy 2021-12-16 10:54:11 -05:00 committed by GitHub
parent 69f6c8d0cd
commit 37f8be093f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions

View File

@ -20,7 +20,7 @@ changelog.
Add that to the PR. Add that to the PR.
If a PR does not warrant a changelog, the CI check for a changelog can be skipped by applying a `changelog-not-required` label on the PR. If a PR does not warrant a changelog, the CI check for a changelog can be skipped by applying a `changelog-not-required` label on the PR. If you are making a PR on a release branch, you should still make a new file in the `changelogs/unreleased` folder on the release branch for your change.
## Copyright header ## Copyright header