Files
@ 7187c1707eda
Branch filter:
Location: kallithea/docs/usage/locking.rst - annotation
7187c1707eda
1.1 KiB
text/prs.fallenstein.rst
tests: restrict pytest test collection to kallithea/tests
When the kallithea root directory contains a populated virtualenv, pytest
would also collect tests in python packages installed there.
Restrict the tests to be considered to any test_*.py file inside
kallithea/tests.
Additionally, by renaming unwanted test files in kallithea/tests/scripts to
_not_ match this pattern, we can completely get rid of the 'norecursedirs'
option.
When the kallithea root directory contains a populated virtualenv, pytest
would also collect tests in python packages installed there.
Restrict the tests to be considered to any test_*.py file inside
kallithea/tests.
Additionally, by renaming unwanted test files in kallithea/tests/scripts to
_not_ match this pattern, we can completely get rid of the 'norecursedirs'
option.
aa17c7a1b8a5 aa17c7a1b8a5 8d065db04909 8d065db04909 8d065db04909 aa17c7a1b8a5 8d065db04909 8d065db04909 03bbd33bc084 03bbd33bc084 8d065db04909 8d065db04909 8d065db04909 aa17c7a1b8a5 8d065db04909 8d065db04909 aa17c7a1b8a5 8d065db04909 8d065db04909 8d065db04909 aa17c7a1b8a5 8d065db04909 8d065db04909 8d065db04909 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`` state that
can be true or false. The hg/git commands ``hg/git clone``, ``hg/git pull``,
and ``hg/git push`` influence this state:
- A ``clone`` or ``pull`` action on the repository locks it (``locked=true``)
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 (``locked=false``) 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 includes 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.
|