# Code integrations (read-only)

**Code** integrations give Sleuth read-only access to your code repositories, allowing Sleuth to analyze your pull requests, commits, files and authors to provide a meaningful and clear view of the changes you make in code when you deploy.

| Integration                                                                                                                                           | Type            | Additional info...                  |
| ----------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | ----------------------------------- |
| [Azure DevOps](/sleuth-dora/integrations-1/code-deployment/azure-devops.md)                                                                           | Code Deployment | Can be used a change source.        |
| [Bitbucket](/sleuth-dora/integrations-1/code-deployment/bitbucket.md)                                                                                 | Code Deployment | Can be used a change source.        |
| [GitHub](/sleuth-dora/integrations-1/code-deployment/github.md)                                                                                       | Code Deployment | Can be used as a change source.     |
| [GitLab](/sleuth-dora/integrations-1/code-deployment/gitlab.md)                                                                                       | Code Deployment | Can be used as a change source.     |
| [Custom Git](https://github.com/sleuth-io/sleuth-gitbook-docs/tree/8c6f655818b14806b9a76252e4224c2ef29d58f6/integrations-1/code-deployment/custom.md) | Code Deployment | Can be used as a change source.     |
| [Terraform Cloud](https://www.terraform.io/cloud)                                                                                                     | Code Deployment | Auto register deploys via a webhook |

### Version Control Workflow

Sleuth encourages and works best with a [trunk-based developmen](https://trunkbaseddevelopment.com/)t workflow. As observed by [Accelerate](https://en.wikipedia.org/wiki/Accelerate_\(book\)):

> Developing off trunk rather than on long-lived branches is correlated with higher delivery performance

#### Scaled trunk-based development

If your teams create short-lived branches that are merged into a core branch (trunk, main, master) at least daily then you're working consistent with commonly accepted continuous integration best practices. Sleuth is an excellent tool for your team.

#### Strict trunk-based development caveats

If your team is small or nimble enough to commit directly to *one* branch, more granular data may not be available or relevant (e.g., review time and review lag time in change lead time) depending on your process and provider. However, Sleuth will still surface the important metrics to help your team succeed in its software delivery optimization goals.


---

# 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/integrations-1/code-deployment.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.