kallithea Files · docs/usage/locking.rst

Files @ 4bd2c3590a22

Branch filter:

Location: kallithea/docs/usage/locking.rst

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

domruf

templates: more consistently put icons inside 'Delete' and 'Edit' buttons

- on repo, repo group, user and user group list page.

For now, we keep the text and keep the button visible.

The Edit button was typically a submit button, not inside a form but inside an
<a>. It did thus not really trigger a submit but just followed the link.

Extracted by Mads Kiilerich.

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