##// END OF EJS Templates
oauth: rename to external identity as it would now be serving both oAuth and SAML
oauth: rename to external identity as it would now be serving both oAuth and SAML

File last commit:

r3133:6afdd8e7 default
r3254:77d66318 default
Show More
extensions-hooks.rst
36 lines | 1.2 KiB | text/x-rst | RstLexer
/ docs / extensions / extensions-hooks.rst
dan
docs: updated docs for integrations, fixes #4137...
r552 .. _extensions-hooks-ref:
Extensions & Hooks
==================
The extensions & hooks section references three concepts regularly,
so to clarify what is meant each time, read the following definitions:
* **Plugin**: A Plugin is software that adds a specific feature to
an existing software application.
* **Extension**: An extension extends the capabilities of,
or the data available to, an existing software application.
* **Hook**: A hook intercepts function calls, messages, or events passed
between software components and can be used to trigger plugins, or their
extensions.
rcextensions: new builtin rcextensions....
r3133
Hooks
-----
Within |RCM| there are two types of supported hooks.
dan
docs: updated docs for integrations, fixes #4137...
r552
rcextensions: new builtin rcextensions....
r3133 * **Internal built-in hooks**: The internal |hg|, |git| or |svn| hooks are
triggered by different VCS operations, like push, pull,
or clone and are non-configurable, but you can add your own VCS hooks,
see :ref:`custom-hooks`.
* **Custom rcextensions hooks**: User defined hooks centre around the lifecycle of
certain actions such are |repo| creation, user creation etc. The actions
these hooks trigger can be rejected based on the API permissions of the
user calling them.
On instructions how to use the custom `rcextensions`
see :ref:`integrations-rcextensions` section.