##// END OF EJS Templates
upstream » kallithea
RSS

Clone from https://kallithea-scm.org/repos/kallithea

tests: fix vcs Hg helper function get_config_value to not modify global state when using a custom config file...
tests: fix vcs Hg helper function get_config_value to not modify global state when using a custom config file This leak was what made test_get_user_name and test_get_user_email pass when test_get_config_value had been run first.
Søren Løvborg - - Load All Authors

File last commit:

r5425:5ae8e644 default
r7307:e885a8ef default
Show More
locking.rst
28 lines | 1.1 KiB | text/x-rst | RstLexer
/ docs / usage / locking.rst
History | Annotation | Raw |Copy content |Copy permalink

Repository locking

Kallithea has a repository locking feature, disabled by default. When enabled, every initial clone and every pull gives users (with write permission) the exclusive right to do a push.

When repository locking is enabled, repositories get a locked flag. The hg/git commands hg/git clone, hg/git pull, and hg/git push influence this state:

  • A clone or pull action locks the target repository if the user has write/admin permissions on this repository.
  • Kallithea will remember the user who locked the repository so only this specific user can unlock the repo by performing a push command.
  • Every other command on a locked repository from this user and every command from any other user will result in an HTTP return code 423 (Locked). Additionally, the HTTP error will mention the user that locked the repository (e.g., “repository <repo> locked by user <user>”).

Each repository can be manually unlocked by an administrator from the repository settings menu.