How suggestions reach GitHub

Send changes to GitHub•4 min read|
|

When you submit review feedback, DraftView maps comments and edits to the PR so authors can apply changes in normal GitHub review flow.

What DraftView sends

  • Review comments
  • Suggested changes for edited chunks
  • Comments on deleted content, anchored to the removed lines in the GitHub diff
  • Replies to existing review threads, and threads you resolved or reopened
  • Attribution to the GitHub identity that posted the review

How DraftView anchors feedback

  • Comments on current text anchor to the matching lines in the PR diff.
  • Comments on deleted content anchor to the removed lines on the base side of the diff, so the thread appears on the deletion itself.
  • Feedback on regions outside the PR diff posts as a file-level comment, and DraftView labels it that way in the submit panel before you submit.

Submission paths

GitHub-linked reviewer

DraftView posts directly to GitHub with that reviewer's account.

DraftView stores feedback as pending team review. A GitHub-linked teammate verifies and pushes it.

Doc reviews

A doc review sends nothing to GitHub until a maintainer finishes it. Then DraftView opens one pull request with the accepted edits and a Markdown record of the review. It posts the comment threads and the edits it didn't apply as review comments on that pull request. See What DraftView sends to GitHub.

What authors see in GitHub

Authors see normal GitHub review comments and suggested changes. They can apply suggestions with standard GitHub controls.