kallithea Files · docs/usage/locking.rst

Files @ a90acf3a1422

Branch filter:

Location: kallithea/docs/usage/locking.rst

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

Søren Løvborg

css: fix redundant/overly broad rules

Remove rule coloring "#content div.panel div.panel-heading .pull-left a"
(and ditto .pull-right) white, as it caused the branch filter drop-down
box on the changelog page to become white-on-white.

I have not found anywhere this rule actually serves a purpose.

On several pages, the rules matched our standard grey buttons, but was
overruled by an !important style for .btn elements.

On repository group pages, it matches the repo group parent path link,
and in /_admin/journal, it matches the "Watched Repositories" and "My
Repositories" links; but all of these are already white from the
"#content div.panel div.panel-heading a" rule.

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