> ## Documentation Index
> Fetch the complete documentation index at: /docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Pull requests

> What Ordyn posts on each pull request and how to control it.

When a pull request opens on your default repository, Ordyn reads the change and posts one review. Draft PRs and PRs from bots are skipped.

## What the review says

The review is short by design. It reports:

* **Expected monitors.** How many monitors Ordyn plans to create for this change and which environment they target. The full list is in the app under **Detect → Pull requests**.
* **Instrumentation gaps.** If a monitor would need telemetry the code does not emit, Ordyn opens a thread on the exact file with what to add. Each thread names the signal it wants to watch and the event or metric that is missing.
* **Access gaps.** If a provider refused Ordyn's read, the review says which permission is missing.

Ordyn only asks for instrumentation when the missing signal would measure customer impact, a broken expectation, or system health. It does not file nice-to-have observability requests.

> [!TIP]
>
> If your branch protection requires conversations to be resolved before merging, unresolved instrumentation threads block the merge. Resolve them, add the telemetry, or skip Ordyn for the PR.

## After the deploy

Once the change reaches production, Ordyn edits the review to reflect what is actually being watched. A monitor that was expected but not created is never left on the PR as a promise.

## Controlling a single PR

From the review footer, any member of your Ordyn workspace can:

* **Skip this PR.** Ordyn withdraws its expected monitors and gap threads for this PR and stops analyzing it. Existing live monitors are not deleted.
* **Re-enable for this PR.** Ordyn starts a fresh analysis at the current head. A merged PR can be re-enabled until its deploy is processed.

Adding the `struct:skip` label to a PR has the same effect as skipping it.

## Drafts in the app

Expected monitors appear as drafts in **Detect → Auto Monitors** until the deploy creates them. You can delete a draft from there. Ordyn will not recreate the same monitor for that PR unless the change materially differs. Live monitors cannot be deleted from the list, because they exist in your provider.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.