Objective
This scripts allows you to keep the organization you work in sync with your local workspace.
The main objective is to centralize your workflow and integrate all the syncronization and cleaning activities you perform daily related to your local file structure and your github organization
How it works
The script mainly relies on your config file “.hubsyncrc” to run all the commands and to customize how to sync your github projects locally
Note: Work ongoing
1 maintainer
Metadata
1 maintainer
Release files for hubsync 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 |
|---|---|---|---|---|
| hubsync-0.2.0.tar.gz | 6.7 kB | Without provenance | Details for hubsync-0.2.0.tar.gz |
Release files / hubsync-0.2.0.tar.gz
| Download URL | hubsync-0.2.0.tar.gz |
|---|---|
| Size | 6.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5b9cc4e8068328c085046a3e95290ab68c434e0e6adc2ea41f2ab460bca55b1a
|
|
BLAKE2b-256 checksum How to use checksums |
074cbf029b0e88f681cdac7e066ffa29b162228f3e67cb33a3a8a1fdf6a397c0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for hubsync 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.
