kallithea Files · docs/usage/locking.rst

Files @ eac20c4b7b20

Branch filter:

Location: kallithea/docs/usage/locking.rst

eac20c4b7b20 1.1 KiB text/prs.fallenstein.rst Show Annotation Show as Raw Download as Raw

Thomas De Schampheleire

style: use monospace for changeset messages

Similar to commits 9005c37dbe21 and 6e65c2153baa that make PR descriptions
display in a monospace font, apply monospace on changeset messages.

Note that in the files template, the reference to the non-existing 'commit'
class can be replaced instead of appending to it.

.. _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.