Mercurial > kallithea
view docs/usage/locking.rst @ 7603:0e8e55f954be
style: avoid double horizontal padding inside panel-body
Only give inline-comments padding if they actually appear inside a diff. General comments already have padding from .panel-body.
Drop padding on changesets columns (next to graphs). The graph already has space, and .panel-body gives spacing to the right.
Drop extra column padding for repo and PR summaries that use columns. The columns already have some padding from .panel-body.
author | Mads Kiilerich <mads@kiilerich.com> |
---|---|
date | Fri, 22 Mar 2019 02:14:36 +0100 |
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.