> For the complete documentation index, see [llms.txt](https://docs.selectstar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.selectstar.com/integrations/dbt/dbt-docs-sync/bitbucket-dbt-docs-sync.md).

# Bitbucket dbt docs Sync

To connect your Bitbucket dbt repository, you will need to follow these steps -

1. Create a Repository Access Token in Bitbucket and grant the following permissions -

* **Read and write access to repositories:** This allows us to ensure we are syncing the descriptions to the updated models.
* **Read and write access to pull request:** This allows us to create or delete a PR and verify that there are no conflicts when generating a PR.

<figure><img src="https://3470314135-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MgAiVthA_yg9UXKuhyY%2Fuploads%2Fgit-blob-caa0d6ef552d2c68cfae58fb095f57bf10af6018%2Fimage.png?alt=media" alt=""><figcaption><p>Create Repository Access Token</p></figcaption></figure>

2. Provide the following information -
   1. Bitbucket Repository URL,
   2. dbt Project name, as mentioned in the `dbt_project.yml` file, and
   3. Root folder (if the dbt project is not in the root folder).

Once this is setup, you will see new PRs generated in your Bitbucket Repo.

<figure><img src="https://3470314135-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MgAiVthA_yg9UXKuhyY%2Fuploads%2Fgit-blob-75d0ff71a4539cbae561cbec6b24a799ae3c2ffe%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.selectstar.com/integrations/dbt/dbt-docs-sync/bitbucket-dbt-docs-sync.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
