kallithea Files · docs/usage/locking.rst

Files @ ac57e45ed903

Branch filter:

Location: kallithea/docs/usage/locking.rst

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

Mads Kiilerich

graph: make sure graph is shown next to the table it belongs to

For some screens sizes (for example around 800 px), the graph with changes
available for PR update wasn't shown next to the corresponding table. The two
boxes would float vertically and be rendered after each other.

To fix that, use the same trick as before 02aef1484695: set the graph height to
0 and give the table a left margin leaving room for the graph.

(The fancyness of Bootstrap grids does in this case seem to only get in the
way. Plain percent would perhaps work better.)

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