Repos
Manage your git repos.
Install
pip install repos
Usage
Inside a directory with several git repos run:
$ repos
Repos in /Users/hello/repos
STATUS NAME BRANCH
──────────────── ──────────────────────────── ──────────
• • 1↑ • • this-is-a-ahead-repo master
• 1↓ • • • this-is-a-behind-repo master
• • • • • this-is-a-clean-repo master
this-is-a-directory/
1± ⚑ • • this-is-a-dirty-repo master
• ⚑ • this-repo-has-no-remotes master
• • • • 3 this-repo-has-three-branches branch-3
• • • 2 • this-repo-has-two-remotes master
1 directories
1 without a remote ⚑
1 without upstream ⚑
1 changed
1 behind
1 ahead
4 clean
To check all available commands:
$ repos help
NAME
repos — Manages your git repos
USAGE
repos # Lists all repos in text format
repos export --json # Exports all repos as json
repos export --yaml # Exports all repos as yaml
repos show REPO # Shows the repo details
repos save # Commits local changes
repos push # Pushes up to the upstream
repos pull # Pulls from the upstream
repos sync # Pull from the upstream and pushes up
repos help # Shows this help
repos version # Prints the current version
Todos
-
Show by default only repos with issues.
-
Show all with the
-a | --allflag. -
Add
clone <url>command to clone a git repo. -
Add
export [file]command to dump all repos, branches and remotes into a file (by defaultrepos.yaml). -
Add
import [file]command to clone repos, branches and remotes from a file (by defaultrepos.yaml). -
Add
config [repo1,repo2] [key] [value]subcommand to store settings in the.git/repo.yamlfile. -
Add
save [repo1,repo2]subcommand to commit all changes. -
Add
pull [repo1,repo2]subcommand to pull all the latest commits from the upstream. -
Add
sync [repo1,repo2]subcommand to commits all changes, pull the latest commits, and push local commits to the upstream. -
Code the
enabledconfig to turn off all other configs. -
Customise the colours via env vars.
Metadata
Release files for repos 0.2.0
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 |
|---|---|---|---|---|
| repos-0.2.0.tar.gz | 15.2 kB | Without provenance | Details for repos-0.2.0.tar.gz |
Release files / repos-0.2.0.tar.gz
| Download URL | repos-0.2.0.tar.gz |
|---|---|
| Size | 15.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dcaf005be9f5b11c13a37eb851d8c9feba3541d70e8122c5b53adb21d326f11b
|
|
BLAKE2b-256 checksum How to use checksums |
3b8dc1169c0fcbb6f1de36b58e1afac2c8521082f71cd7a11e645767aa8b2221
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.6
|
Security for repos 0.2.0
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.