##// 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
repo-locking.rst
14 lines | 586 B | text/x-rst | RstLexer

Repository Locking

Repository locking means that when a user pulls from a |repo|, only a push by that user will unlock it. This allows an Admin to pull from a |repo| and ensure that no changes can be introduced. You need Admin access to the |repo| to enable |repo| locking. To enable |repo| locking, use the following steps.

  1. From the |RCE| interface, select :menuselection:`Admin --> Repositories`, then :guilabel:`Edit` beside the |repo| you wish to lock.
  2. From the left-hand pane, select :menuselection:`Advanced --> Lock Repository`