Gitea CLI
Simple gitea cli
Usage
Usage: gitea-cli [-h] [-u USERNAME] [-p PASSWORD] [--api API] [--url URL] {repo} ...
Gitea CLI - Interact with Gitea API
Positional Arguments:
{repo}
repo Repository operations
Options:
-h, --help show this help message and exit
-u, --username USERNAME
Gitea username
-p, --password PASSWORD
Gitea password
--api API Gitea API token/key
--url URL Gitea API endpoint URL
Usage: gitea-cli repo [-h] [-a REPO_NAME] [-l] [-rm REPO_NAME] [-m REMOTE_URL] [--service {git,github,gitlab,gogs,gitea,codeberg}] [--mirror] [-n REPO_NAME] [--organization ORG_NAME] [--private]
[-fk OWNER/REPO] [--clone-user CLONE_USER] [--clone-pass CLONE_PASS] [--clone-token CLONE_TOKEN] [--no-wiki] [--no-labels] [--no-issues] [--no-pull-requests] [--no-releases]
[--no-milestones]
Options:
-h, --help show this help message and exit
-a, --add REPO_NAME Create new repository
-l, --list List repositories
-rm, --remove REPO_NAME
Remove repository
-m, --migrate REMOTE_URL
Migrate/clone repository from remote server (GitHub, GitLab, Gogs, private Git)
--service {git,github,gitlab,gogs,gitea,codeberg}
Remote Git service type (default: git)
--mirror Set repository as a continuously syncing mirror
-n, --name REPO_NAME Target repository name on Gitea
--organization ORG_NAME
Target organization on Gitea (optional)
--private Make target repository private on Gitea
-fk, --fork OWNER/REPO
Fork repository (e.g. owner/repo_name)
Source Repository Credentials:
--clone-user CLONE_USER
Username for remote repo authentication (HTTPS Basic Auth)
--clone-pass CLONE_PASS
Password for remote repo authentication
--clone-token CLONE_TOKEN
Personal Access Token for remote repo (GitHub/GitLab/Gitea token)
Migration Scope Options:
--no-wiki Do not migrate wiki
--no-labels Do not migrate labels
--no-issues Do not migrate issues
--no-pull-requests Do not migrate pull requests
--no-releases Do not migrate releases
--no-milestones Do not migrate milestones
👤 Author
Metadata
Release files for gitea-cli 0.12.4
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 | Actions |
|---|---|---|---|---|
| gitea_cli-0.12.4.tar.gz | 8.9 kB | Without provenance | Details for gitea_cli-0.12.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| gitea_cli-0.12.4-py3-none-any.whl | Python 3 | none | any | Details for gitea_cli-0.12.4-py3-none-any.whl |
Total release size: 16.5 kB
Release files / gitea_cli-0.12.4.tar.gz
| Download URL | gitea_cli-0.12.4.tar.gz |
|---|---|
| Size | 8.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
70dcb4be9bbed9e75da5b53be2dca6802eb6170873d67c63c8736b83043234a3
|
|
BLAKE2b-256 checksum How to use checksums |
f5bc1eaadd8c1956390776abfb1077e98374f00208dc9e1afdf5de7dc715075a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.4
|
Release files / gitea_cli-0.12.4-py3-none-any.whl
| Download URL | gitea_cli-0.12.4-py3-none-any.whl |
|---|---|
| Size | 7.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c1e1280d3cb6c7242f06c41217d4deab042ca051b289bdd3b6c5ccb0425cd606
|
|
BLAKE2b-256 checksum How to use checksums |
28832ef6530a94598d6603005efffef21baabd0fb5a00609554f431a2a60d561
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.4
|
Security for gitea-cli 0.12.4
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.