This…will likely take some time to mature. And is a hack.
The broad intent is to provide a Git repository context at the file level (over SSH). In essence on entering the context, a path to an ephemeral cleartext tree (top of master) of the remote repository will be returned, and on exit that same tree will be removed.
Intended use is for system configuration data maintained and managed via Git – ie update the data in git and the dependent tools reconfigure to match when they run, sort of using Git as a hacky etcd.
1 maintainer
Metadata
1 maintainer
Release files for gitfiles_ctx 0.1.post11
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 | |
|---|---|---|---|---|
| gitfiles_ctx-0.1.post11.tar.gz | 21.3 kB | Without provenance | Details |
Release files / gitfiles_ctx-0.1.post11.tar.gz
| Download URL | gitfiles_ctx-0.1.post11.tar.gz |
|---|---|
| Size | 21.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
14a091c00974bf75d5c8e18ea3e10b8049181632e2aef5a71a8df0a219e4568d
|
|
BLAKE2b-256 checksum How to use checksums |
4c0506bf35c5c0b1c400b9bee713e327548b8e7d3f4a949d64209d96cb2a921f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for gitfiles_ctx 0.1.post11
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.
