git996
one command to sync multiple git repositories.
I always have serveral git repositories to sync between home and company everyday.It's too tiring to sync repo one by one.This tool is used to sync all the repos one command.
Actually, git996 just enter every repo and execute git pull for you
Install
Install from PyPi
$pip3 install git996
Uninstall from PyPi
$pip3 uninstall git996
$rm ~/.git996.toml
Install from source code
$git clone https://github.com/chengyi818/git996
$cd git996
$python3 setup.py install --user
This will install git996 to ~/.local/bin,so maybe you need to add ~/.local/bin to PATH.
Uninstall from source code
$python3 setup.py install --user --record log
$cat log | xargs rm -rf
$rm ~/.git996.toml
Usage
1. create config file
$git996 init
This command will create config file in ~/.git996.toml.
2. modify config file
You should modify config file according your situation.
return_if_dirty
True
git996 will print all path of dirty repo, then git996 will exit
False
git996 will ignore dirty repo,just pull clean repo.
3. sync all repositories
$git996 sync
TODO
- Think about local branch ahead/behind origin stackoverflow
LiCENSE
Anti-996 License, See the LICENSE file.
Metadata
Release files for git996 0.0.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 |
|---|---|---|---|---|
| git996-0.0.4.tar.gz | 4.4 kB | Without provenance | Details for git996-0.0.4.tar.gz |
Release files / git996-0.0.4.tar.gz
| Download URL | git996-0.0.4.tar.gz |
|---|---|
| Size | 4.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1d1b25652d1837e9118a8a04fcd2215870304665dee2286f9ec23d37c1a98f25
|
|
BLAKE2b-256 checksum How to use checksums |
56c7840084ab0567c5a96e3854ca8a5cb725eab4daa84645be516437469396bc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.18.4 setuptools/36.7.2 requests-toolbelt/0.9.1 tqdm/4.32.1 CPython/3.5.2
|
Security for git996 0.0.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.