# Code deployments

Sleuth uses your code repositories as its main sources of change. Setting up a code deployment in Sleuth allows us to track and alert on what goes into every code deploy. A code deploy surfaces all the **pull requests, linked issues, commits and authors** included in every deploy. This information allows Sleuth to:

* Track your deployment's Accelerate DevOps metrics
  * Deploy frequency, change lead time, change failure rate, MTTR and deploy size
* [Lock deployments](/sleuth-dora/modeling-your-deployments/code-deployments/deployment-locking.md) so you can pump the brakes on deploying when needed
* Slice and dice past deploys with [powerful search](/sleuth-dora/modeling-your-deployments/code-deployments/search.md)
* Highlight [drift between your different deployment environments](/sleuth-dora/modeling-your-deployments/code-deployments/environment-drift.md)
* Sleuth [automatically tag deploys](/sleuth-dora/modeling-your-deployments/code-deployments/tags.md) based on the code that's changed
* and much more...

<figure><img src="/files/Qx82Gl7l2kNpLhyvVGyI" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.sleuth.io/sleuth-dora/modeling-your-deployments/code-deployments.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
