Review Repository Branches
Use document review when Markdown is in a repository but not necessarily in a pull request.
Open A Document Review
- Open /.
- Paste a repository, branch, folder, or Markdown file URL.
- Click
Open review.
For GitHub, Commentary accepts repository roots, /tree/... URLs, and /blob/... Markdown URLs. For Azure DevOps, use a project-scoped repository, PR, branch, folder, or file URL when possible.
What Changes In Document Review
- The same reading shell is used.
- The page is labeled as repository document review instead of pull request review.
- There is no
Submit reviewbutton. Refresh documentreplacesRefresh PR.- Comments stay app-native in Commentary.
Branch, Folder, And File Navigation
- The file navigator lists Markdown files from the selected branch or folder.
- Use the branch selector to switch branch context when available.
- Use folder view for docs-heavy repositories.
- Use
Latestfor reading andDifffor branch-backed change inspection. - Use the commit selector when you need to inspect one document change set.
Best Use Cases
- specs that need early feedback before implementation is ready
- ADRs and product docs living on a shared branch
- README and docs maintenance outside a PR moment
- AI-generated docs that should be reviewed before a merge request exists
Important Difference From PR Review
Document review does not submit a provider review event. It is designed for app-native collaboration around repository Markdown.