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

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

config: initialize routes directly from RootController...
config: initialize routes directly from RootController Let RootController directly initialize routes instead of app_cfg injecting the mapper. For test initialization, we also need a handle to the mapper. We could either recreate it (but fragile if the real mapper initialization is changed later) or obtain it from a fresh RootController. This commit opts for the latter.
Søren Løvborg - - Load All Authors

File last commit:

r5425:5ae8e644 default
r6530:69cd0c05 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.