gh-prlist
Configurable GitHub pull-request monitoring with clickable macOS
notifications. The PyPI package is gh-prlist (prlist and pr-list
are taken or blocked as too similar). The installed commands are gh-prlist,
pr-list, and prlist. It requires the GitHub CLI (gh) to be installed and
authenticated.
uvx gh-prlist setup
uvx gh-prlist list
uvx gh-prlist monitor
uvx gh-prlist monitor --own
uvx gh-prlist monitor --team
uvx gh-prlist monitor --own --team
setup writes TOML configuration to ~/.prlist. Command-line options
override that file; run prlist <command> --help for all overrides.
The default policies show your open non-draft PRs with failing CI and
non-draft team-review requests with green CI and no explicit merge conflict.
monitor checks every ten minutes and writes a clickable report to
~/.cache/prlist/prs.html.
Each source can independently filter CI (green, failing, any) and
mergeability (not_conflicting, conflicting, any). Notifications can
include own PRs, team PRs, or both. Change-only notification state persists
across monitor restarts.
Failure ignores are configurable per source as case-insensitive check-name
substrings. They can be entered during setup or supplied repeatedly:
gh-prlist monitor --own --own-ignore-failure "Post Plan Checks"
Each source can also require labels, which is how you narrow a team-review
queue to one team's routing label. label_match = "any" (the default) keeps a
PR carrying at least one of the labels; "all" requires every one of them:
gh-prlist monitor --team --team-label "teams/engineering-enablement"
gh-prlist monitor --team --team-label "teams/ee" --team-label "release" --team-label-match all
Labels are matched case-insensitively after the search, so PRs dropped by the
filter still appear in the report's "filtered out" section, marked label filter. CI is only fetched for label matches, so narrowing by label makes a
monitor cycle cheaper rather than more expensive.
For clickable notification actions on macOS, install terminal-notifier.
Without it, notifications fall back to osascript.
Metadata
Release files for gh-prlist 0.3.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 | |
|---|---|---|---|---|
| gh_prlist-0.3.0.tar.gz | 23.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gh_prlist-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 44.6 kB
Release files / gh_prlist-0.3.0.tar.gz
| Download URL | gh_prlist-0.3.0.tar.gz |
|---|---|
| Size | 23.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5bf2a76c20a5a69eb6bc52ecabd5bcd0fae38db8acf53e62243879342254b20f
|
|
BLAKE2b-256 checksum How to use checksums |
97d365a96ab879e66a6512227cfad6092c75e327212219db51e20385a9784803
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.12
|
Release files / gh_prlist-0.3.0-py3-none-any.whl
| Download URL | gh_prlist-0.3.0-py3-none-any.whl |
|---|---|
| Size | 21.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
528949d403cee7a068136b0ef5ee2c4218346bf3374f1ffc12a782ec6e2f7acc
|
|
BLAKE2b-256 checksum How to use checksums |
d6308f1424ba656d86f2cac3e492ffeb88da4111abeeac2c6535a17cc3d9e61e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.12
|
Security for gh-prlist 0.3.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.