##// END OF EJS Templates
pull-requests: add merge check that detects WIP marker in title. This will prevent merges in such case....
pull-requests: add merge check that detects WIP marker in title. This will prevent merges in such case. Usually WIP in title means unfinished task that needs still some work. This pattern is present in Gitlab/Github and is already quite common.

File last commit:

r645:c8c27324 default
r4099:c12e69d0 default
Show More
redmine.rst
28 lines | 913 B | text/x-rst | RstLexer
dan
docs: updated docs for integrations, fixes #4137...
r552 .. _integrations-redmine:
Redmine integration
===================
.. important::
docs: updated integrations docs fix #4137
r645 Redmine integration is only available in |RCEE|.
dan
docs: updated docs for integrations, fixes #4137...
r552
.. important::
docs: updated integrations docs fix #4137
r645 In order to make issue numbers clickable in commit messages, see the section
:ref:`rhodecode-issue-trackers-ref`. Redmine integration is specifically for
altering Redmine issues.
dan
docs: updated docs for integrations, fixes #4137...
r552
docs: updated integrations docs fix #4137
r645 Redmine integration allows you to reference and change issue statuses in
Redmine directly from commit messages, using commit message patterns such as
``fixes #235`` in order to change the status of issue 235 to eg. "Resolved".
dan
docs: updated docs for integrations, fixes #4137...
r552
docs: updated integrations docs fix #4137
r645 To set a Redmine integration up, it is first necessary to obtain a Redmine API
key. This can be found under *My Account* in the Redmine application.
You may have to enable API Access in Redmine settings if it is not already
available.
Once you have the API key, create a Redmine integration as outlined in
dan
docs: updated docs for integrations, fixes #4137...
r552 :ref:`creating-integrations`.