Mercurial > kallithea
view docs/usage/locking.rst @ 5979:0bb4fa32a75a
tests: Mercurial hooks must use ui.status for messages sent to the client
Mercurial changed so sys.stdout and sys.stderr now are intercepted instead of
being sent to the client. That caused a regression that
manual_test_vcs_operations.py test_push_new_file_hg caught - we no longer
reported 'Repository size' to the user.
The issue was introduced by a Mercurial change, but the fix is backwards
compatible with Mercurial 2.9.
The fix is to use ui.status everywhere. ui is a Mercurial thing, but
handle_git_receive also creates a ui object for Git hooks so ui.status can be
used there too.
| author | domruf <dominikruf@gmail.com> |
|---|---|
| date | Tue, 03 May 2016 00:12:55 +0200 |
| parents | 5ae8e644aa88 |
| children |
line wrap: on
line source
.. _locking: ================== 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.