##// END OF EJS Templates
shadow-repos: use safer way to destroy shadow repositories....
shadow-repos: use safer way to destroy shadow repositories. we had reported errors on removal of shadow repos. Not reproduced, however suspecting are filesystem sync/symlink race-conditions on shared storage. End result were existing shadow-repo directories that tricked rhodecode into thinking shadow repos is existing, but infact it was a dummy structure semi-removed. Using shutil.move we ENSURE rhodecode doesn't read those back even if removal fails.

File last commit:

r645:c8c27324 default
r2791:27d869d5 stable
Show More
slack.rst
20 lines | 755 B | text/x-rst | RstLexer
dan
docs: updated docs for integrations, fixes #4137...
r552 .. _integrations-slack:
Slack integration
=================
docs: updated integrations docs fix #4137
r645 To set a Slack integration up, it is first necessary to set up a Slack webhook
API endpoint for your Slack channel. This can be done at:
dan
docs: updated docs for integrations, fixes #4137...
r552
https://my.slack.com/services/new/incoming-webhook/
docs: updated integrations docs fix #4137
r645 Select the channel you would like to use, and Slack will provide you with the
webhook URL for configuration.
You can now create a Slack integration as outlined in
:ref:`creating-integrations`.
.. note::
Some settings in the RhodeCode admin are identical to the options within the
Slack integration. For example, if notifications are to be sent in a private
chat, leave the "Channel" field blank. Likewise, the Emoji option within
RhodeCode can override the one set in the Slack admin.