summaryrefslogtreecommitdiff
path: root/doc/push_rules
diff options
context:
space:
mode:
authorTakuya Noguchi <takninnovationresearch@gmail.com>2019-06-28 13:25:56 +0000
committerRémy Coutable <remy@rymai.me>2019-06-28 13:25:56 +0000
commitaf5da7564edab1d3f2457e13e3157f2806b0b9a0 (patch)
tree3974da0ab5be197ac4256ed2b297216275042e38 /doc/push_rules
parent423c4c43cb73c72e8b27d7c091f392e3a09be354 (diff)
downloadgitlab-ce-af5da7564edab1d3f2457e13e3157f2806b0b9a0.tar.gz
Replace 'JIRA' with 'Jira'
https://community.atlassian.com/t5/Jira-questions/Is-it-quot-JIRA-quot-or-quot-Jira-quot/qaq-p/681163 Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>
Diffstat (limited to 'doc/push_rules')
-rw-r--r--doc/push_rules/push_rules.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/push_rules/push_rules.md b/doc/push_rules/push_rules.md
index b2d626a0a74..2142f5a5f69 100644
--- a/doc/push_rules/push_rules.md
+++ b/doc/push_rules/push_rules.md
@@ -26,11 +26,11 @@ Every push rule could have its own use case, but let's consider some examples.
Let's assume you have the following requirements for your workflow:
-- every commit should reference a JIRA issue, for example: `Refactored css. Fixes JIRA-123.`
+- every commit should reference a Jira issue, for example: `Refactored css. Fixes JIRA-123.`
- users should not be able to remove git tags with `git push`
All you need to do is write a simple regular expression that requires the mention
-of a JIRA issue in the commit message, like `JIRA\-\d+`.
+of a Jira issue in the commit message, like `JIRA\-\d+`.
Now when a user tries to push a commit with a message `Bugfix`, their push will
be declined. Only pushing commits with messages like `Bugfix according to JIRA-123`