helga-reviewboard
A helga plugin for expanding shortcodes for code reviews on ReviewBoard. This matches the pattern \bcr(\d+)\b and requires configuring the setting REVIEWBOARD_URL. For example:
<sduncan> can someone look at cr1234 <helga> sduncan might be talking about codereview: http://example.com/r/1234
This match plugin will also show links for any code review match it finds:
<sduncan> can someone look at cr1234 and cr456 <helga> sduncan might be talking about codereview: http://example.com/r/1234, http://example.com/r/456
Settings
- REVIEWBOARD_URL
A URL string format for showing ReviewBoard links. This should contain a format parameter ‘{review}’. (default: ‘http://localhost/{review}’)
License
Copyright (c) 2015 Shaun Duncan
Licensed under an MIT license.
1 maintainer
Metadata
1 maintainer
Release files for helga-reviewboard 0.2.0
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 | |
|---|---|---|---|---|
| helga-reviewboard-0.2.0.tar.gz | 2.6 kB | Without provenance | Details |
Release files / helga-reviewboard-0.2.0.tar.gz
| Download URL | helga-reviewboard-0.2.0.tar.gz |
|---|---|
| Size | 2.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f939778f1f49107ff4ac8f5bc2251d4ddf99977f81f5b829407ad17aa5f8de64
|
|
BLAKE2b-256 checksum How to use checksums |
602d72b6e49e4cd56b71b6dc053f5476c4f151e74b4a4c5f37ec1b8396687437
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for helga-reviewboard 0.2.0
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.
