Files @ 6563dfd8c890
Branch filter:

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

6563dfd8c890 1.1 KiB text/prs.fallenstein.rst Show Source Show as Raw Download as Raw
Mads Kiilerich
less: style panel headings with variables the same way as the (inverse) navbars are styled

No visible change by default, but splitting these variables out separately and
explicitly makes the system more flexible and prepare for future changes or
customizations.

@panel-primary-heading-bg already indirectly defaulted to
@kallithea-theme-main-color.

@panel-primary-text defaulted to white and would have to be customized anyway
if using a light background.
.. _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.