Some basic functionality to execute stuff here and there.
what’s in the box?
This library aims to ease the implementation of custom git flows.
For that purpose a libary to manage name prefixes and the like is provided. And since a lot of code flows are part of a deployment strategy, object wrappers for remote hosts and directories are also included.
A flow can be implemented as a separate module, and used flexibly (like dry-running) if that module is made available to the packaged commandline-tool, and requested in the flow configuration (via the ‘module’ section/key). Shaping out that is part of the current development, as well as adding more the object mapper classes (git branches/remotes, local/remote files, etc).
Check out the github repository for more related code, like the tests and the two (still raw) flow modules that already exist.
1 maintainer
Metadata
1 maintainer
Release files for flowlib 0.6.6.8
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 | |
|---|---|---|---|---|
| flowlib-0.6.6.8.tar.gz | 28.9 kB | Without provenance | Details |
Release files / flowlib-0.6.6.8.tar.gz
| Download URL | flowlib-0.6.6.8.tar.gz |
|---|---|
| Size | 28.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fd751124e038bd8dd579c0304bb011fc1fab35fe21e61fc6b5a2453b27f78d64
|
|
BLAKE2b-256 checksum How to use checksums |
d8e9bfe54667f27c084648a86142d897d6413391382247913270817349f8a198
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for flowlib 0.6.6.8
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.
