diff options
| author | Drew Blessing <drew@blessing.io> | 2016-02-04 19:38:02 +0300 |
|---|---|---|
| committer | Drew Blessing <drew@blessing.io> | 2016-02-04 19:38:02 +0300 |
| commit | e932714e09d0f1c21363c329d602b4f10e56e65f (patch) | |
| tree | 66401d3341717fd6d5bec697f097ec6be9618437 | |
| parent | ac923b4fb40da88d6c7907d08d4584d5d4a560e2 (diff) | |
| parent | f835fa8d750b3b8b13b3b6e24780c1e4e01b9796 (diff) | |
Merge branch 'doc_bug' into 'master'
fix documentation bug / typo
Hey, noticed this a little bit ago. Need to get the example matching up with the following explanation.
See merge request !2709
| -rw-r--r-- | doc/customization/issue_closing.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/customization/issue_closing.md b/doc/customization/issue_closing.md index 00edfc97ed9..194b8e00299 100644 --- a/doc/customization/issue_closing.md +++ b/doc/customization/issue_closing.md @@ -16,7 +16,7 @@ Here, `%{issue_ref}` is a complex regular expression defined inside GitLab, that For example: ``` -git commit -m "Awesome commit message (Fix #20, Fixes #21 and Closes group/otherproject#2). This commit is also related to #17 and fixes #18, #19 and https://gitlab.example.com/group/otherproject/issues/23." +git commit -m "Awesome commit message (Fix #20, Fixes #21 and Closes group/otherproject#22). This commit is also related to #17 and fixes #18, #19 and https://gitlab.example.com/group/otherproject/issues/23." ``` will close `#18`, `#19`, `#20`, and `#21` in the project this commit is pushed to, as well as `#22` and `#23` in group/otherproject. `#17` won't be closed as it does not match the pattern. It also works with multiline commit messages. |