Mercurial > kallithea
view docs/usage/locking.rst @ 5107:5153c491a964
comments: show status changes as a part of the comment instead of in the header
This makes it obvious what the user said and there is no reason to explain what
he is saying or where he is saying it.
Comments will always have a text or a status change - there is no need for "No
comments".
author | Mads Kiilerich <madski@unity3d.com> |
---|---|
date | Thu, 07 May 2015 16:26:40 +0200 |
parents | 8d065db04909 |
children | 5ae8e644aa88 |
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`` state that can be true or false. The hg/git commands ``hg/git clone``, ``hg/git pull``, and ``hg/git push`` influence this state: - A ``clone`` or ``pull`` action on the repository locks it (``locked=true``) 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 (``locked=false``) 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 includes 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.