How DraftView works
DraftView runs a human-in-the-loop review process for AI-generated documentation pull requests on top of GitHub.
The AI review loop
- AI or a teammate opens a documentation pull request.
- DraftView ingests the PR into a queue.
- A human reviewer reads, comments, and edits in a visual review surface.
- DraftView syncs that feedback to GitHub.
- AI pushes an updated commit.
- Reviewer verifies whether that commit addressed the original feedback region.
- Maintainer or admin signs off.
- Team merges in GitHub.
Team queue lifecycle
Connected repositories feed an org queue automatically. Each queue item tracks a lifecycle state:
- New
- In review
- Changes requested
- Waiting on AI
- Addressed
- Stalled
- Signed off
- Ready to merge
- Merged
See full definitions in Pull request lifecycle states.
Live review surface
When a PR head moves, DraftView updates the review session quickly.
- You see a banner when a newer revision is available.
- You can switch to a focused view that shows changes since your last review.
- Draft edits rebase onto the latest content when possible, so reviewer work is not lost.
External review links
External links are snapshot-based by design.
- DraftView captures the PR state at link creation time.
- External reviewers always review that same snapshot.
- If the PR moves later, reviewers see a staleness notice and can request a new link.
Sign-off and oversight
Maintainers and admins can sign off queue items.
Sign-off records who approved, at which head SHA, and with which CI status. Governance plan orgs can export audit records and view oversight metrics.