Review the docs in a pull request as documents
Rendered Review opens the Markdown and MDX files in a GitHub pull request as formatted pages. Select the words you mean and comment on them. Every comment is saved to the pull request in GitHub, so reviewers who stay in GitHub see it too.
Or put renderedreview.dev/ in front of any pull request URL.
An 18-second loop. A reviewer selects "retries failed deliveries indefinitely" in a rendered RFD and comments: "Indefinitely? The proposal caps it at 8 tries. Should the summary say until the cap?" They publish it, and the thread appears in the comment rail, joined to the phrase by a connector line. Then the same comment is shown on the pull request in GitHub as a review comment on line 12.
- GitHub.com
- Markdown and MDX
- Mermaid and other diagrams
- Keyboard and screen reader
Three steps, and GitHub stays in charge
No new place to keep comments. Rendered Review reads the pull request from GitHub and writes your feedback back to it.
Open the pull request
Paste a pull request URL, follow the link the GitHub Action posts on the PR, or change
github.com/…torenderedreview.dev/github.com/….Read and select
Changed and unchanged docs render as pages, with changed sections marked. Select a phrase, sentence, table cell or diagram and write your comment.
Publish to GitHub
Your comment is posted to the pull request in the closest form GitHub supports. The next section shows which.
Where your comment ends up
Rendered Review keeps no copy of your review. Each comment becomes a GitHub object that anyone on the pull request can read and answer.
- You select text on a changed linedocs/rfd/0042-webhook-retries.md
Each delay includes full jitter of up to 20% so recovering endpoints are not hit at once.
priya-k commented on line 24Review threadfull jitter of up to 20%
"Full jitter" usually means random in [0, delay). Which one do we mean?
- You select text the PR didn't change, in a changed filedocs/rfd/0042-webhook-retries.md
The dispatcher retries failed deliveries indefinitely, holding a worker slot for days.
priya-k commented on the fileFile commentretries failed deliveries indefinitely
Do we know how long the longest one ran? A number here would make the case.
- You comment on a document the PR didn't touchdocs/reliability.md
Webhook consumers must respond within 10 seconds.
jlo commentedPR commentdocs/reliability.md · permalink @ e41f0c210 seconds
Does the new timeout change this?
- You suggest a change on a changed linedocs/rfd/0042-webhook-retries.md
After the
lastfinal attempt the event moves to the dead-letter queue.mchen suggested a changeGitHub suggestionAfter the last attemptAfter the final attemptThe author can apply it from GitHub with one click.
Comments made directly in GitHub show up in Rendered Review too, so it doesn't matter where each reviewer works.
Built for reading, not diffing
Markdown and MDX
GitHub Flavored Markdown, front matter and alerts. MDX components show as labelled source, and nothing in the file is run.
Diagrams, rendered
Mermaid, Graphviz, Vega, WaveDrom, maps and STL models render in the browser. Comment on the diagram or its source.
Comments survive revisions
After a push, comments are matched to the new text. Uncertain matches are marked outdated, never dropped.
Unchanged docs too
Switch from changed docs to all docs and comment on any Markdown file in the repository at that commit.
One link per pull request
An optional GitHub Action posts a single Rendered Review link on each PR that changes Markdown.
Open source
AGPL-3.0-only. The code is on GitHub, and issues and pull requests are welcome.
Free for public repositories
Private repositories are priced by active private contributors: people who publish through Rendered Review in a month. Reading is always free.Who you pay forReading is always free.Reviewers who only read, or who comment directly in GitHub, never count toward your plan.
Public
Open-source and public projects
Unlimited public activity
Open a pull request (opens in new tab)Individual
Personal private repositories
1 active private contributor
Start 30-day trial (opens in new tab)Team
Small engineering teams
10 active private contributors
Additional active contributors: $5/month each
Start 30-day trial (opens in new tab)Business
Growing companies
50 active private contributors
Additional active contributors: $4/month each
Start 30-day trial (opens in new tab)Scale
Larger engineering organizations
200 active private contributors
Additional active contributors: $3/month each
Start 30-day trial (opens in new tab)Additional contributors never cost more than the next plan. Nobody is blocked mid-review.
Enterprise
300 or more active private contributors plus enterprise services. For GHES, legal, security, SLA, and support requirements.
Annual agreement, priced for your organization.
Self-hosting
Free under AGPL-3.0-only, with no plan limits. Commercial licenses and support are available.
Every paid plan includes
- Rendered review for changed and unchanged Markdown.
- Contextual comments and replies.
- Native and extended suggestions.
- Historical and resolved discussions.
- GitHub-originated comment interoperability.
- Annotation validation and fallback behavior.
- PR deep links and GitHub Action integration.
Who counts as an active private contributor? A unique GitHub user who performs at least one write action through Rendered Review in a private repository during the billing month: publishing a comment or reply, submitting a review, creating a suggestion, or resolving or reopening a reconstructed thread.
These don't count:
- Reading.
- Unpublished local drafts.
- Activity performed directly in GitHub.
- Repeated actions by an already active user.
- Public-repository activity.
- Automated webhook or GitHub Action activity.
30-day private-repository trial with Team capacity for up to 10 active private contributors. No credit card. It starts when the first private document is opened.
Start with the part you need
Self-hosting
Run your own instance on Cloudflare Workers, with the steps for sign-in and a custom domain.
Deploy itAnnotation format
How comments record their anchor in GitHub, and how they fall back.
Read the specObservability
What the server logs, and what it never logs.
See the eventsExternal resources
Why images from other servers never load without you asking.
Read about privacyTry it on a pull request you're reviewing
Public repositories are free and need no setup.