Repository navigation
0.2.1 — installable from PyPI, and three hosted-build fixes
2026-09-04 · 4 commits since v0.2.0
Install without a checkout
uv tool install pull-request-view # or: pipx install pull-request-view
prview startThe PyPI name is pull-request-view. An unrelated project owns prview there —
also a GitHub PR tool. A hyphen alone is not enough to clear it: PEP 503 normalization
treats pr-view and prview as distinct, but PyPI's separate similarity check strips
separators, collapses both to prview, and rejects the upload with a 400. The command
it installs is still prview, and the import package is still prview.
Releases publish through Trusted Publishing, so no API token exists in the repo — the
first upload included, via a pending publisher registered before the project existed.
The release workflow installs the built wheel into a clean venv and fetches assets over
HTTP before uploading: server.py mounts prview/static at runtime, so a wheel missing
those files imports cleanly and then 404s everything an import check would never notice.
Fixes
- The overview no longer dies on any PR past a few hundred lines. Every model in
WebLLM's prebuilt list ships a 4096-token window, and prview's prompt budget is sized
forclaudeat 200,000 characters. A 30 KB diff produced an 11,735-token prompt and
the run failed outright. The worker now asks for 8192, and the browser engine asks for
a prompt built to a 16,000 character budget that bounds the description, the file
table, the diffs and the omitted-file list — each of which overran the window on its
own. An unbudgeted prompt is byte-identical to before, soclaudeis untouched. - The keyboard-shortcut bar is back.
#appis a100vhflex column and the hosted
token bar was a sibling above it, so the column ran past the viewport and the action
bar — Viewedv· Explaine· Aska· Commentc· Flagf— was clipped with
no way to scroll to it. - Explain-selection answers in the browser. Selecting diff lines only ever called
the job endpoint, which a static page cannot serve, so it reported "this engine needs
the local app" while already on the in-browser engine.
Upgrading
uv tool install pull-request-view (first time) or uv tool upgrade pull-request-view.
The hosted build is a URL and updates itself.