routing: use a common method to extract the f_path for repo views....

routing: use a common method to extract the f_path for repo views. The extra slashes can cause odd issues with GIT, the previous pylons code had a fix in routing. This ports this fix into pyramid helper in base app.

lisaq - - Load All Authors

File last commit:

r645:c8c27324 default


                r1929:0c7b3df6

default

Download file

             redmine.rst
        
                    28 lines
            
             | 913 B
            
                | text/x-rst
            
             |
                RstLexer

/ docs / integrations / redmine.rst

History | Annotation | Raw |Copy content |Copy permalink

Redmine integration

Important

Redmine integration is only available in |RCEE|.

Important

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.

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 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 :ref:`creating-integrations`.

	Site-wide shortcuts
/	Use quick search box
g h	Goto home page
g g	Goto my private gists page
g G	Goto my public gists page
g 0-9	Goto bookmarked items from 0-9
n r	New repository page
n g	New gist page

	Repositories
g s	Goto summary page
g c	Goto changelog page
g f	Goto files page
g F	Goto files page with file search activated
g p	Goto pull requests page
g o	Goto repository settings
g O	Goto repository access permissions settings
t s	Toggle sidebar on some pages