ghsync: GitHub Repo Syncer
This script uses the GitHub API to get a list of all forked, mirrored, public, and private repos in your GitHub account. If the repo already exists locally, it will update it via git-pull. Otherwise, it will properly clone the repo.
It will organize your repos into the following directory structure:
+ repos \ +-- forks (public fork repos) +-- mirrors (public mirror repos) +-- private (private repos) +-- public (public repos) +-- watched (public watched repos)
Requires Ask Solem’s github2 (http://pypi.python.org/pypi/github2).
Inspired by Gisty (http://github.com/swdyh/gisty).
Install
To install ghsync, simply run:
$ pip install ghsync
The command ghsync will then be available to you from the command line. Beware, unless you set the GHSYNC_DIR environment variable, it will add all the repos to your current directory.:
$ export GHSYNC_DIR='~/repos/'
Options
If the --upsteam argument is passed, all forked repos will have an upstream remote added, pointing to their parent repo on GitHub.
You can also selectively sync certian types of repos with --only. If you’d like to only sync forked repositories, for example:
$ ghsync --only forks
Contribute
If you’d like to contribute, simply fork the repository, commit your changes to the develop branch (or branch off of it), and send a pull request.
Metadata
Release files for ghsync 0.3.1
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 |
|---|---|---|---|---|
| ghsync-0.3.1.tar.gz | 3.3 kB | Without provenance | Details for ghsync-0.3.1.tar.gz |
Release files / ghsync-0.3.1.tar.gz
| Download URL | ghsync-0.3.1.tar.gz |
|---|---|
| Size | 3.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f8ed754200074c7bd6ae46c743455255853006f06757b05f4aa4e9efb8fcc96c
|
|
BLAKE2b-256 checksum How to use checksums |
b56fd6cdc30c07fbfc2cfa14ae01f37afba64d670cfb214186558d12e0021201
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for ghsync 0.3.1
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.