ribbity
Hop, frog, hop!
Turn a bunch of GitHub issues into a mkdocs site.
For example, turn the sourmash-bio/sourmash-examples issue tracker into this site.
Project information
You can see the introductory blog post here: Announcing ribbity - a hacky project to build Web sites from GitHub issue trackers.
tl;dr Ribbity turns GitHub issue trackers into mkdocs sites that can be hosted via GitHub pages.
If you want to see ribbity in action, we have a sandbox repo where you can play with it a bit!
- first, add an issue over at ribbity-sandbox!
- then, go to the rendered sandbox site and search for your issue text!
See ribbity documentation here and visit the source code on GitHub.
Ribbity is released under the BSD 3-Clause license.
Please file issues on GitHub.
Metadata
Release files for ribbity 0.4.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 |
|---|---|---|---|---|
| ribbity-0.4.1.tar.gz | 18.3 kB | Without provenance | Details for ribbity-0.4.1.tar.gz |
Release files / ribbity-0.4.1.tar.gz
| Download URL | ribbity-0.4.1.tar.gz |
|---|---|
| Size | 18.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e412c74a0d2d6d8a28723d5caf40589dee5a52e7457ce49e46960c3fcafa00f4
|
|
BLAKE2b-256 checksum How to use checksums |
d40d2e1c287d479b95309d0d9fe90b5fe5584729f33f2cf78aa939323b9deb2f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.8.13
|
Security for ribbity 0.4.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.