##// END OF EJS Templates
scm-app: allow to set documented pyro4 as scm_app_implementation....
scm-app: allow to set documented pyro4 as scm_app_implementation. The documented ini setting allows to set pyro4 as scm_app, while the backend code crashes on import of pyro4 module. This change allows to configure the app based on the .ini docs. if we pass pyro4 as backedn, we simply skip import and use the default pyro4 scm_app

File last commit:

r552:9a0f45b0 default
r632:064401fe default
Show More
redmine.rst
25 lines | 893 B | text/x-rst | RstLexer
dan
docs: updated docs for integrations, fixes #4137...
r552 .. _integrations-redmine:
Redmine integration
===================
.. important::
In order to make issue numbers clickable in commit messages see the
:ref:`rhodecode-issue-trackers-ref` section. The Redmine integration
only deals with altering Redmine issues.
.. important::
Redmine integration is only available in |RCEE|.
The 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``
To set a Redmine integration up it is first necessary to obtain a Redmine api
key. This can be found in ``My Account`` in the Redmine application.
If it is not there, you may have to enable API Access in Redmine settings.
Once you have the api key, create a ``redmine`` integration in
:ref:`creating-integrations`.