aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCalMWolfs <94038482+CalMWolfs@users.noreply.github.com>2024-10-07 21:16:35 +1100
committerGitHub <noreply@github.com>2024-10-07 21:16:35 +1100
commit266d007da9f23b19f8e815da3005451195a33a5e (patch)
treee87a0aad35d1706a2c0bf128c8487a13fd4168eb
parent1de910a9ae9ab96fa75044367f9546d671fbcba1 (diff)
downloadskyhanni-266d007da9f23b19f8e815da3005451195a33a5e.tar.gz
skyhanni-266d007da9f23b19f8e815da3005451195a33a5e.tar.bz2
skyhanni-266d007da9f23b19f8e815da3005451195a33a5e.zip
its actually a plus (#2689)
-rw-r--r--pull_request_template.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/pull_request_template.md b/pull_request_template.md
index dba81f46b..02769a0f8 100644
--- a/pull_request_template.md
+++ b/pull_request_template.md
@@ -1,6 +1,6 @@
<!-- remove all unused parts
-The title of your PR should be descriptive and concise. It should be in the format of `Type: Description`. For example, `Feature: Add new command` or `Fix: Bug in command`. If there are multiple types of changes these can be separated by an ampersand. For example, `Feature & Fix: Add new command and fix bug in command`.
+The title of your PR should be descriptive and concise. It should be in the format of `Type: Description`. For example, `Feature: Add new command` or `Fix: Bug in command`. If there are multiple types of changes these can be separated by a plus. For example, `Feature + Fix: Add new command and fix bug in command`.
## PR Reviews