pelican-link-bugs
Automatically link bug/issue references in content to a tracker.
By default it will link pull-requests and issues for github in the following formats:
* I should reiview PR mozilla/bedrock#1. * Don't forget to watch issue twbs/bootstrap#2.
It will also link to Mozilla’s bugzilla instance:
Need a laugh? Read bug 765645.
You can easily replace these or add to them with a setting:
BUG_TRACKERS = {
# key is the regex
r'issue +(?P<bug_repo>[a-z1-9-_/]+)#(?P<bug_id>\d+)':
# value is URL template with keywoard substitutions
'https://github.com/{bug_repo}/issue/{bug_id}',
}
You can also import BUG_TRACKERS from pelican_bugs and modify it. If you need to alter how the links look, you can set BUG_LINK_TEMPLATE. The link template can use bug_url and bug_text keywords:
# default template
BUG_LINK_TEMPLATE = '<a href="{bug_url}">{bug_text}</a>'
Metadata
Release files for pelican-link-bugs 0.2
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 |
|---|---|---|---|---|
| pelican-link-bugs-0.2.tar.gz | 2.6 kB | Without provenance | Details for pelican-link-bugs-0.2.tar.gz |
Release files / pelican-link-bugs-0.2.tar.gz
| Download URL | pelican-link-bugs-0.2.tar.gz |
|---|---|
| Size | 2.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6eeb537fdf9d57adc3c0d88ce68c884aa0945bb318ca3a5a8e727c956ec2b1ad
|
|
BLAKE2b-256 checksum How to use checksums |
5a05494528ca646a5ba14e1b315d9d743609ea206deb83b7f975d311b2916518
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pelican-link-bugs 0.2
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.