> For the complete documentation index, see [llms.txt](https://sandgarden.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sandgarden.gitbook.io/docs/working-with-doc-holiday/review-and-revise.md).

# Review and Revise

When a Work History entry reaches **Ready for Review**, open its sheet and review each file. From there, you can confirm the request details, leave comments, and open the final pull request or merge request.

### Opening the entry

1. In Work History, select the entry marked **Ready for Review**.
2. The sheet opens with **Details**, **Files**, and **Messages**; recent work requests can also show a **Reasoning** tab. The **Messages** tab shows the conversation thread and the reply box.
3. In **Details**, confirm these labels:
   * **Summary:** the request title
   * **Created By:** who started the entry
   * **Started:** when the work began
   * **Last Updated:** the latest activity
   * **Trigger:** what started the work
   * **Status:** **Ready for Review**
   * **Pull Request:** the docs repo link, when one exists
   * **Merged by:** who merged it, when the entry has already been merged

### Reviewing proposed file changes

The **Files** tab shows each file row, its diff count, and its status. Open a file to review the diff.

![The work item's Files tab showing a file diff with a Doc Holiday comment](/files/lYrWwF1CbjoVT5iwR3JS)

Inside the diff, review the lines in order. In the diff gutter, use **Comment on this line, or drag to select multiple** to anchor a comment; **Extend comment to this line** grows the selection. Use **Add Comment** to leave feedback, **Send to Doc** to send the comment for another revision pass, or **Add to Batch** to collect several comments first. Use **Add a file-level comment** when the note applies to the whole file. Expand hidden context with **Expand unchanged lines**, and close open sections with **Collapse all expanded sections**.

### Commenting and revising

Leave inline comments on the file content when only a few lines need attention. Leave a file-level comment when the whole file needs a broader change. In **Messages**, reply with **Send a message** and then **Send** so the next update includes that context. **Add Comment** records feedback without starting work. **Send to Doc**, **Send Batch to Doc**, and messages in the **Messages** tab send the feedback to Doc Holiday for a revision pass.

If you selected several comments, finish with **Send Batch to Doc**.

### Excluding files

Use the icon-only buttons whose tooltips read **Discard file** and **Restore file** to remove a file from the final request or bring it back. The confirmation dialog updates to show how many files stay in the request and how many are permanently discarded.

### Approving and opening the pull request

When the draft looks right, use **Open Pull Request** on GitHub or **Open Merge Request** on GitLab. The confirmation dialog shows how many files will be committed and how many will be permanently discarded.

After approval, the opened request is a normal pull request or merge request in the docs repo, and the standard merge flow applies. If Slack notifications are configured, Doc Holiday posts the Slack notification after merge. See [Slack notifications](/docs/automation-and-integrations/slack-notifications.md).

### Next steps

Continue with [Work History](/docs/working-with-doc-holiday/work-history.md).