Glerbl is a tool to help manage git hooks and promote consistent coding standards among contributors to a repository.
Let’s say you maintain a github repository for which you want to ensure the following coding standards:
No trailing spaces.
No non-ascii file names.
All python code must conform to pep8.
You can hope that contributors will remember to run the necessary checks before they send in pull requests or push code to the repository.
Or you can use glerbl to formalize your requirements and provide all collaborators with the means to detect problems and fix these problems before they commit.
1 maintainer
Metadata
1 maintainer
Release files for glerbl 0.1.1
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 |
|---|---|---|---|---|
| glerbl-0.1.1.tar.gz | 21.8 kB | Without provenance | Details for glerbl-0.1.1.tar.gz |
Release files / glerbl-0.1.1.tar.gz
| Download URL | glerbl-0.1.1.tar.gz |
|---|---|
| Size | 21.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c3b43d067bd8788db3654858396e1f4ae94d0e00bb1a0e8062785dc67e74e6f4
|
|
BLAKE2b-256 checksum How to use checksums |
0408314c8f6bd9d988db4960055be5df95c3aa59c2a57e7bbd2f84af39de2371
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Python-urllib/2.7
|
Security for glerbl 0.1.1
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.
