github-status
A simple interface for updating SHA1s for PRs with statuses. Made for Jenkins initially, altough a command line tool, it mostly consumes environment variables to set states on commits.
Github Environment Variables:
GITHUB_REPOSITORY The url part of the repo, like ceph/ceph
GITHUB_SHA A commit SHA that will receive the update
GITHUB_OAUTH_TOKEN Generated TOKEN to authenticate to Github
GITHUB_STATUS_CONTEXT The “title” part of the status, like “docs”
GITHUB_STATUS_STARTED The ‘started’ text that will change next to the ‘title’ (context)
GITHUB_STATUS_SUCCESS The ‘success’ text that will change next to the ‘title’ (context)
GITHUB_STATUS_FAILURE The ‘failure’ text that will change next to the ‘title’ (context)
GITHUB_STATUS_ERROR The ‘error’ text that will change next to the ‘title’ (context)
GITHUB_STATUS_STATE The state for the sha1, one of: ‘success’, ‘error’, ‘failure’, or ‘pending’
Build Environment Variables:
BUILD_URL A url that points to the actual full url for the build
PARENT_BUILD_URL Optional parent url where actual build happened
Metadata
Release files for github-status 0.0.6
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 |
|---|---|---|---|---|
| github-status-0.0.6.tar.gz | 4.9 kB | Without provenance | Details for github-status-0.0.6.tar.gz |
Release files / github-status-0.0.6.tar.gz
| Download URL | github-status-0.0.6.tar.gz |
|---|---|
| Size | 4.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2969cca366531693124c65e2218b320444f4cc7feb4517779e8426d7b3b5ff6d
|
|
BLAKE2b-256 checksum How to use checksums |
3f333cc3f6cf0c0bd0694361e65b072de337810ae7e25d555034686eebc84b2a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for github-status 0.0.6
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.