kallithea Files · docs/usage/locking.rst

Files @ 228dd29e79da

Branch filter:

Location: kallithea/docs/usage/locking.rst

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

domruf

less: clean up changelog style

- use table-layout: fixed
Since we already use a fixed width for the most cells, this makes it easier
(faster) for the browser to render specially big tables.
And it allows to use 'text-overflow: ellipsis'. The old ellipsis settings
have no effect.

- use nowrap and 'text-overflow: ellipsis' for all cells
A table is easier (faster) to read for a user if all the row have the same height.
Therefore don't wrap lines and in case of overflow use ellipsis.

- remove unnecessary height
Up until now the row was bigger then 31px so this had no effect.
And it look wrong to make the row bigger then its content.

- remove unnecessary border-color
bootstrap default is almost the same color

- remove unnecessary text-align
left is the default

- remove font-size or use bootstrap .small
Making fonts too small hurts the readability.

- remove some padding and margin

- don't use special colors
The differences are hardly noticable or in case of the gray dates hurt readability.

- remove obsolete table#changesets .logtags style

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