##// END OF EJS Templates
integrations: refactor/cleanup + features, fixes #4181...
integrations: refactor/cleanup + features, fixes #4181 * added scopes on integrations, scopes are: - repo only - repogroup children only - root repos only - global (any repo) * integrations schemas now have separate section for the settings (eg. slack) and options (eg. scope/enabled) * added descriptions to integration types * added icons to integration types * added 'create new' integration page * added scope of integration to integrations list * added breadcrumbs for each repo/repogroup/global integrations pages * added sorting to integrations list * added pagination to integrations list * added icons to integrations list * added type filter to integrations list * added message to integrations list if none we found * added extra permissions check on integrations views * db migration from 56 => 57 - adds child_repos_only field * added tests for integrations triggered on events * added tests for integrations schemas * added tests for integrations views for repo/repogroup/admin

File last commit:

r1:854a839a default
r731:7a6d3636 default
Show More
notifications-overview.rst
22 lines | 716 B | text/x-rst | RstLexer
/ docs / collaboration / notifications-overview.rst
project: added all source files and assets
r1 Notifications Overview
----------------------
|RCM| has an integrated notification system which alerts users to requests
that they have received. Notifications can occur for the following reasons:
* Pull request reviews
* Commit message mentions
When someone opens a |pr| on one of your |repos|, or adds you as a |pr|
reviewer, you will receive a notification in |RCE| and an email,
if not configured see :ref:`set-up-mail`. Also, during the review process you
receive notifications on the following actions:
* New comments
* Status changes
* Inline code review comments
Each notifications provides a link to take you directly to the issue.
.. image:: ../images/notifications.png
:alt: Notifying Colleagues