Files
@ 97a99ced3b85
Branch filter:
Location: kallithea/docs/usage/locking.rst - annotation
97a99ced3b85
1.1 KiB
text/prs.fallenstein.rst
less: remove borders and padding around navbar items
Navbar items were styled with borders to look like embossed areas that could be
clicked. The top menu also had it in the drop-down menu, while the context menu
didn't.
The areas are big, and it is quite clear it is some kind of clickable menu ...
and the clickable area is also highlighted when hovering. We can thus do
without the borders and get a slightly cleaner look.
Navbar items were styled with borders to look like embossed areas that could be
clicked. The top menu also had it in the drop-down menu, while the context menu
didn't.
The areas are big, and it is quite clear it is some kind of clickable menu ...
and the clickable area is also highlighted when hovering. We can thus do
without the borders and get a slightly cleaner look.
aa17c7a1b8a5 aa17c7a1b8a5 8d065db04909 8d065db04909 8d065db04909 aa17c7a1b8a5 5ae8e644aa88 8d065db04909 03bbd33bc084 03bbd33bc084 5ae8e644aa88 5ae8e644aa88 8d065db04909 aa17c7a1b8a5 5ae8e644aa88 8d065db04909 aa17c7a1b8a5 8d065db04909 5ae8e644aa88 8d065db04909 aa17c7a1b8a5 8d065db04909 8d065db04909 5ae8e644aa88 8d065db04909 aa17c7a1b8a5 8d065db04909 8d065db04909 | .. _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.
|