> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/integrations-in-avo-assure/versioning/bitbucket.md). # Bitbucket Avo Assure seamlessly integrates with Bitbucket, enabling test artifacts to be pushed into and pulled from the Bitbucket repository. This integration supports effective version management of artifacts such as the Element Repository folder, Test Case folder, Data Table, and Execution List. The Bitbucket repository acts as a secure storage space, facilitating team collaboration on shared artifacts. ### This Document Includes [**Prerequisites**](/avo-assure/integrations-in-avo-assure/versioning/bitbucket/prerequisites.md)\ Pre-requisites for Bitbucket Integration. [**Generating Bitbucket API Token**](/avo-assure/integrations-in-avo-assure/versioning/bitbucket/bitbucket-api-token-generation.md)\ Steps to generate API token in Bitbucket. [**Configuring Bitbucket in Avo Assure**](/avo-assure/integrations-in-avo-assure/versioning/bitbucket/configuring-bitbucket-in-avo-assure.md)\ Steps for instructions on configuring Bitbucket. [**Bitbucket Actions**](/avo-assure/integrations-in-avo-assure/versioning/bitbucket/version-history.md)\ Steps to view and manage the version actions in Bitbucket. --- # 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.avoautomation.com/avo-assure/integrations-in-avo-assure/versioning/bitbucket.md?ask=&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.