kallithea Files · docs/usage/locking.rst

Files @ 9d972ac5437b

Branch filter:

Location: kallithea/docs/usage/locking.rst

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

Thomas De Schampheleire

admin: remove named references to web analytics services

Étienne Gilli mentioned via a Weblate comment that Piwik is now Matomo
( https://matomo.org/blog/2018/01/piwik-is-now-matomo/ ), and suggested
changing the string in the code base.

But in fact, there is no real reason to mention any one service. In fact,
since the Kallithea project does not endorse any service, it is better to
not list anything.

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