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

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

tests: fix failures due to environment LANG settings (Issue #286)...
tests: fix failures due to environment LANG settings (Issue #286) When the environment in which the tests are run dictates a non-English language (e.g. via LANG=de_DE.UTF-8), certain tests started to fail because formencode validation messages where translated in that language. A test failing this way is for example test_create_in_group_without_needed_permissions in kallithea/tests/functional/test_admin_repos.py . This is a regression of commit 3b29103657df (i18n: remove explicit formencode language setting), but in fact reverting it is not the right solution as there is no problem except during test execution. Instead, force the formencode language to 'empty' (meaning English) for test execution only. See also http://www.formencode.org/en/latest/i18n.html
Søren Løvborg - - Load All Authors

File last commit:

r5425:5ae8e644 default
r6694:c20abcf4 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.