Kira Setup Bot
CLI utility to automate routine work with new projects.
Part of the @kira bots family.
kira-setup does not create a repository. It configures an existing GitLab
project so new repositories start with the same engineering standards.
Features
- Configures GitLab project defaults for a stricter merge flow
- Requires passing pipelines before merge
- Requires all discussions to be resolved before merge
- Sets fast-forward only merge strategy
- Configures merge request approval rules
- Protects the
masterbranch and release tags matchingv* - Enforces push rules for branch names and commit messages
- Prevents secret pushes and enables member checks
- Creates a standard label set for triage and workflow
- Configures container registry cleanup policy
Installation
Requirements:
- Python 3.11+
- An existing GitLab project
- A GitLab access token with permission to manage project settings
pip install kira-setup
Quick Start
Run the CLI against an existing project:
kira-setup group-or-user/project-name --token YOUR_ACCESS_TOKEN
For self-hosted GitLab:
kira-setup group-or-user/project-name \
--token YOUR_ACCESS_TOKEN \
--domain gitlab.example.com
To skip specific setup steps, repeat --skip with the stable step name:
kira-setup group-or-user/project-name \
--token YOUR_ACCESS_TOKEN \
--skip labels \
--skip protect-tags
Available --skip values:
starconfigurepush-rulesapproval-ruleslabelsprotect-branchesprotect-tagscleanup-policy
Why Use It
We use this CLI to make repository setup repeatable across projects.
Instead of applying the same GitLab rules manually every time, kira-setup
brings a new repository to the expected baseline in a single command.
Related Projects
kira: the full bots familykira-stale: stale issue and pull request automationkira-release: automated semantic releases
Metadata
Release files for kira-setup 0.2.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| kira_setup-0.2.2.tar.gz | 7.5 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| kira_setup-0.2.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 17.3 kB
Release files / kira_setup-0.2.2.tar.gz
| Download URL | kira_setup-0.2.2.tar.gz |
|---|---|
| Size | 7.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f8c721c4ed4dae05e5965a0c516bfca057e9ad0fac083713b49d2f91d040df10
|
|
BLAKE2b-256 checksum How to use checksums |
b032bdd5d7d26cb42ff035e240e58ac75947673284bc1c6c684f4e84650011be
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 19, 2026.
Transparency logRelease files / kira_setup-0.2.2-py3-none-any.whl
| Download URL | kira_setup-0.2.2-py3-none-any.whl |
|---|---|
| Size | 9.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
98c5ff316a02ad0537e427a516f6fbf9ff17a20a044e645f008ed8ef492c101c
|
|
BLAKE2b-256 checksum How to use checksums |
4a037d2061d29666eb3b96865cc29cc9060e745fd645a52b11f4df2992fc8d42
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 19, 2026.
Transparency logSecurity for kira-setup 0.2.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for kira_setup-0.2.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 19, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.