summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKubernetes Prow Robot <k8s-ci-robot@users.noreply.github.com>2021-12-21 12:44:01 -0800
committerGitHub <noreply@github.com>2021-12-21 12:44:01 -0800
commit01647f33e3525516613cd0acf1f428ab2b4d826a (patch)
treee00add9b21e51c4203ce5ecd5982c6cc5a0b1c4f
parentd3933637179ef00f4c6a95f161c6a18f6bc52f1d (diff)
parenta4873c6e8c85204e390a953b6e0d61f4c08f37a6 (diff)
Merge pull request #6181 from avinashupadhya99/reword-blocked-words-in-commit-message
Reword github keywords usage in PR and commit messages
-rw-r--r--contributors/guide/pull-requests.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/guide/pull-requests.md b/contributors/guide/pull-requests.md
index fb20c4fe..242e0bc9 100644
--- a/contributors/guide/pull-requests.md
+++ b/contributors/guide/pull-requests.md
@@ -444,7 +444,7 @@ commit message will automatically apply the `do-not-merge/invalid-commit-message
label to your PR preventing it from being merged.
[GitHub keywords] in a PR to close issues is considered a convenience item, but
-can have unexpected side-effects; often closing something they shouldn't.
+can have unexpected side-effects *when used in a commit message*; often closing something they shouldn't.
**Blocked Keywords:**
- close