git_repo_manager allows users to create new git repositories based on a well defined template.
Repositories can be managed directly via git-repo-manager.py script or by developer himself. In this last case, developer just have to import simple_manage as a python module.
It also create a Jenkins Job for this new born repo.
1 maintainer
Metadata
1 maintainer
Release files for git-repo-manager 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 | |
|---|---|---|---|---|
| git-repo-manager-0.2.0.tar.gz | 3.2 kB | Without provenance | Details |
Release files / git-repo-manager-0.2.0.tar.gz
| Download URL | git-repo-manager-0.2.0.tar.gz |
|---|---|
| Size | 3.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7079be5d3ae70c909db7a0f62c41e3cdcca87b567ed1f521d23ea7e0aee873a6
|
|
BLAKE2b-256 checksum How to use checksums |
540fb389d64111d233a2bfedd86f86de1187a09bc8a8f914eeec9e6bc8ae7611
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for git-repo-manager 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.
