> ## Documentation Index
> Fetch the complete documentation index at: https://context7-enes-docs7-docs.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Branch Previews

> A stable preview URL for every branch, posted to the pull request

Open a pull request and Docs7 deploys a preview of it. Each branch gets **one stable URL** that is overwritten in place on every push, so the link in your pull request always shows the latest commit:

```
https://preview--<owner>--<repo>--<branch>-<hash>.docs7.io
```

Long branch names are shortened in the label; the trailing hash keeps the URL unique and stable.

## Pull request integration

Preview deployments post:

* a `docs7/preview` commit status on the pushed commit, and
* a single comment on the open pull request with the preview link, edited in place on later pushes, never duplicated.

## What triggers a preview

* Only `push` events to branches in the repository itself build; pushes to forks are ignored. Tags, releases, and opening a pull request do not build.
* Pushing the configured production branch deploys production instead.
* Deleting a branch on GitHub, or closing or merging its pull request, tears down the preview: the URL, the deployment target, everything. Deleting the production branch does nothing.

## The preview cap

A site can hold 5 live branch previews on Free and 50 on Pro (see [Limits](/docs7/limits)). Past that, pushes to new branches are refused and reported as a failed `docs7/preview` commit status; pushes to branches that already have a preview keep working. Clear previews by deleting merged branches on GitHub or closing their pull requests.

## Previews vs production

Previews build exactly like production with two differences: they never carry the custom-domain base path, and Context7 indexing only applies to production deployments.