Files @ 8ba69bf9236e
Branch filter:

Location: kallithea/docs/usage/locking.rst - annotation

8ba69bf9236e 1.1 KiB text/prs.fallenstein.rst Show Source Show as Raw Download as Raw
Mads Kiilerich
style: fix changeset tag container - fix vertical alignment of right aligned tags

Tags and comment count were not aligned with the line text at all, and a solid
background were hiding the separator lines and made it look even more messy.

extra-container and comments-container are now simplified with top right
positioning and less margin tweaking.

Minimal changes to the tags - just touching some external sizing so it fits in
the container: line-height and margin.
.. _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.