> 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/request-work-in-git.md).

# Request Work in Git

Mention `@doc.holiday` in the thread you are already using. Doc Holiday starts the request there. Put `@doc.holiday` first or within the first few words, then describe the change.

### Where it works

* GitHub: issue comments, pull request comments, pull request review bodies, pull request review comments, and new issue bodies.
* GitLab: issue notes, merge request notes, and new issue bodies.
* Bitbucket: pull request comments.
* Linear: issue comments and new issue bodies. If Linear is not connected yet, see [Connect Linear](/docs/sources/connect-linear.md).

For new issue bodies, the mention must appear within the first few words.

### What happens next

Doc Holiday reacts to your comment, replies in the same thread, and keeps the response with the request. Follow-up comments on the pull request Doc Holiday opened continue the same Work History entry. A second request on the originating issue gets a reply pointing you to that linked pull/merge request. Make change requests there, or open a new issue for net-new work.

### Help shortcut

Use `@doc.holiday help` when a short reminder is enough. Doc Holiday returns inline usage help and examples.

### Example requests

On a pull request that changed behavior:

```
@doc.holiday this PR renames the `timeout` config key to `request_timeout`.
Update /docs/configuration.md to match; leave the retries section alone.
```

On an issue asking for a missing page:

```
@doc.holiday write a troubleshooting page for webhook delivery failures.
Cover signature mismatches and retry behavior; base it on webhooks/handler.go.
```

A follow-up comment on the pull request Doc Holiday opened, after reviewing the draft:

```
@doc.holiday the example in the new page uses the v1 payload.
Switch it to the v2 shape from webhooks/payload.go.
```

Name the outcome and the page you want; when a file matters, give its path. [Writing requests](/docs/prompting-guide/writing-requests.md) covers the craft in full.

### Verify

The request appears in [Work History](/docs/working-with-doc-holiday/work-history.md).