GitHub Repos Cloner
Because GitHub delete is permanent.
Motivation
Yes there are others, now there is this one too.
Todo
Explain motivation better.
Install
Install:
$ {easy_install, pip} github_repo_cloner
Usage
Use like so:
$ github_repo_cloner USER_OR_ORG
Example
In this example, all of the plone org’s repos will be cloned/updated to the cwd:
$ github_repo_cloner plone
History
0.0.3 - 2012/08/02
Fix project name
0.0.2 - 2012/08/02
Metadata fix
0.0.1 - 2012/08/02
First release
1 maintainer
Metadata
1 maintainer
Release files for github_repos_cloner 0.0.3
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 | |
|---|---|---|---|---|
| github_repos_cloner-0.0.3.zip | 626.8 kB | Without provenance | Details |
Release files / github_repos_cloner-0.0.3.zip
| Download URL | github_repos_cloner-0.0.3.zip |
|---|---|
| Size | 626.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1675d99e1a9f10d48aece7faa5c84a1f7d68ea4e366ac1038bc1d73d21803532
|
|
BLAKE2b-256 checksum How to use checksums |
95bd27a3e0015810595e9a053df87b3013730151a476eee4cf3c962ca3422d66
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for github_repos_cloner 0.0.3
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.
