Files
@ 67cb7f56d7f4
Branch filter:
Location: kallithea/docs/usage/locking.rst - annotation
67cb7f56d7f4
1.1 KiB
text/prs.fallenstein.rst
tests: vcs: use _BackendTestMixin instead of duplicated BackendBaseTestCase in test_filenodes_unicode_path
test_inmemchangesets.py hosts a second base class in addition to
_BackendTestMixin, which is basically a duplication we want to get rid of.
As that duplicated base class BackendBaseTestCase is still in use by
test_filenodes_unicode_path.py, we first need to let that test use the main
base class.
test_inmemchangesets.py hosts a second base class in addition to
_BackendTestMixin, which is basically a duplication we want to get rid of.
As that duplicated base class BackendBaseTestCase is still in use by
test_filenodes_unicode_path.py, we first need to let that test use the main
base class.
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.
|