rhodecode-enterprise-ce Files · docs/extensions/extensions-hooks.rst

pull-requests: add merge check that detects WIP marker in title. This will prevent merges in such case....

pull-requests: add merge check that detects WIP marker in title. This will prevent merges in such case. Usually WIP in title means unfinished task that needs still some work. This pattern is present in Gitlab/Github and is already quite common.

marcink - - Load All Authors

File last commit:

r3290:ac4e4e5a default


                r4099:c12e69d0

default

Download file

             extensions-hooks.rst
        
                    36 lines
            
             | 1.2 KiB
            
                | text/x-rst
            
             |
                RstLexer
            
             / docs / extensions / extensions-hooks.rst
          
                    History
                
                 |
                  Source
                 | Raw
                 |Copy content
                 |Copy permalink

        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.

        marcink
    
rcextensions: new builtin rcextensions....

              r3133
            
      Hooks

      -----

        marcink
    
docs: added SAML documentation....

              r3290
            
      Within |RCE| there are two types of supported hooks.

        dan
    
docs: updated docs for integrations, fixes #4137...

              r552
            
        marcink
    
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.

	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

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.

marcink rcextensions: new builtin rcextensions....	r3133
		Hooks
		-----

marcink docs: added SAML documentation....	r3290	Within \|RCE\| there are two types of supported hooks.
dan docs: updated docs for integrations, fixes #4137...	r552
marcink 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.