summaryrefslogtreecommitdiff
path: root/contributors
diff options
context:
space:
mode:
authorAvinash Upadhyaya K R <52544819+avinashupadhya99@users.noreply.github.com>2021-10-26 14:33:46 +0530
committerGitHub <noreply@github.com>2021-10-26 14:33:46 +0530
commitf1279464b0af0e72e6a74d74b4f90e666fa7201a (patch)
treede631a97079349f1337084d48f23d9da83d8b795 /contributors
parentfa66358d6a024e5151204693fa24eeba24237b73 (diff)
Reword github keywords usage in PR and commit messages
Diffstat (limited to 'contributors')
-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..27b342d1 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