This is the administration documentation. There is a separate [user documentation](../user/project/issues/managing_issues.md#closing-issues-automatically)
There is a separate [user documentation] on issue closing pattern.
on issue closing pattern.
When a commit or merge request resolves one or more issues, it is possible to
When a commit or merge request resolves one or more issues, it is possible to
automatically have these issues closed when the commit or merge request lands
automatically have these issues closed when the commit or merge request lands
...
@@ -13,8 +13,8 @@ in the project's default branch.
...
@@ -13,8 +13,8 @@ in the project's default branch.
In order to change the pattern you need to have access to the server that GitLab
In order to change the pattern you need to have access to the server that GitLab
is installed on.
is installed on.
The default pattern can be located in [`gitlab.yml.example`] under the
The default pattern can be located in [`gitlab.yml.example`](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/config/gitlab.yml.example)
"Automatic issue closing" section.
under the "Automatic issue closing" section.
> **Tip:**
> **Tip:**
You are advised to use <http://rubular.com> to test the issue closing pattern.
You are advised to use <http://rubular.com> to test the issue closing pattern.
...
@@ -31,7 +31,7 @@ Because Rubular doesn't understand `%{issue_ref}`, you can replace this by
...
@@ -31,7 +31,7 @@ Because Rubular doesn't understand `%{issue_ref}`, you can replace this by