##// END OF EJS Templates
rhodecode-enterprise-ce
RSS
db: Change ordering of test env setup and db connection init....
db: Change ordering of test env setup and db connection init. - DB init sets rhodecode.model.db.ENCRYPTION_KEY - Test env setup resets rhodecode.model.db.ENCRYPTION_KEY to None - Therefore DB init has to be done after test env setup.
marcink - - Load All Authors

File last commit:

r1:854a839a default
r117:25511505 default
Show More
repo-locking.rst
14 lines | 586 B | text/x-rst | RstLexer
/ docs / collaboration / repo-locking.rst
History | Annotation | Raw |Copy content |Copy permalink

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`