> 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/configuring-bitbucket-in-avo-assure/copy-of-pushing-data-to-bitbucket-repository.md).

# Pushing Data to Bitbucket Repository

The Push method in Avo Assure sends the latest test artifacts to the Bitbucket repository. It is used in the following scenarios:

* Creating new test artifacts, such as Element Repository, Test Cases, Data Tables, or Execution Lists.
* Updating or modify existing test artifacts to save the latest version in Bitbucket.
* Sharing updated test artifacts with the team through Bitbucket.
* Maintaining version history of automation assets for safety and traceability.

### Pushing Test cases to Bitbucket Repository

From Avo Assure, the following test artifact data can be pushed to Bitbucket for version control:

* Element Repository
* Test Case
* Data Table
* Execution List

{% hint style="info" %}
**Note:** The steps explained below remain the same for all supported artifacts.
{% endhint %}

{% hint style="info" %}
**Note**: The steps remain the same for all artifacts. Navigate to the respective artifact page, select the required data or parent folder, and push it to Bitbucket.
{% endhint %}

To push Test cases to Bitbucket Repository, perform the following actions:

1. On the **Home** page, under **Projects**, select the required **Project**.
2. Select the **Design Studio** button > **Test Case** tab.
3. Select the **Bitbucket** icon and then select **Push**. The **Commit Test Cases** dialog opens.

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

4. In the **Search** textbox, enter a keyword to filter the test cases.
5. Select the **Status** dropdown to filter the test cases by status.
6. Select **Hide checked in artifacts** to exclude already checked in items.
7. Under **Name**, expand the folders, and then select the required test cases.

{% hint style="info" %}
**Note**:

* The **Status** column displays the workflow status of test artifact.
* The **Checked in** column displays the workflow status of test artifact.
  {% endhint %}

8. Select the **Branch** dropdown to choose the Bitbucket branch.
9. In the **Commit message** textbox, enter the description of the push changes.

{% hint style="info" %}
**Note**: (Optional) Select the required options:

* **Push associated Element Repository**: Allows you to push the associated element repository of the selected test artifact to the Bitbucket.
* **Push associated Data Table**: Allows you to push the associated data table of the selected test artifact to the Bitbucket.
  {% endhint %}

10. Select **Push** to commit and push the selected test cases to Bitbucket. After selecting **Push**, a success message appears. The Client console also provides a confirmation message indicating whether all test artifacts were successfully pushed to Bitbucket.

{% hint style="info" %}
**Note**:

* During the process of pushing test artifacts to Bitbucket, the Avo Assure Client Console provides real-time updates throughout the Commit phase, showing the ongoing progress. After the commit is completed successfully, a single push is triggered automatically to Bitbucket.
* You can also compare the test artifacts. For more information, refer to [Comparison](/avo-assure/integrations-in-avo-assure/versioning/bitbucket/configuring-bitbucket-in-avo-assure/comparing-test-artifacts.md) article.
  {% endhint %}

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

<figure><img src="/files/9H8oeRNr0RvW53bJf6lz" alt=""><figcaption></figcaption></figure>

### Pushing Data Table to Bitbucket Repository

To push Data Table to Bitbucket Repository, perform the following actions:

1. On the **Home** page, under **Projects**, select the required Project.
2. Select the **Manage Integrations**. The **Test Data Management** page opens.
3. Select the **Bitbucket** icon and then select **Push**. The **Commit Data Tables** dialog opens.

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

5. In the **Search** textbox, enter a keyword to filter the data tables.
6. Select the **Status** dropdown to filter the data tables by workflow status.
7. Select **Hide checked in artifacts** to exclude already checked in items.
8. Under **Name**, expand the folders, and then select the required data tables.

{% hint style="info" %}
**Note**:

* The **Status** column displays the workflow status of data table.
* The **Checked in** column indicates whether a data table is already pushed to Bitbucket.
* You can view the total number of selected Data Tables.
  {% endhint %}

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

6. Select the **Branch** dropdown to choose the Bitbucket branch.
7. In the **Commit message** textbox, enter the description of the push changes.
8. Select **Push** to commit and push the selected data tables to Bitbucket. After selecting **Push**, a success message appears. The Client console also provides a confirmation message indicating whether all data tables were successfully pushed to Bitbucket.

{% hint style="info" %}
**Note**: During the process of pushing data tables to Bitbucket, the Avo Assure Client Console provides real-time updates throughout the Commit phase, showing the ongoing progress. After the commit is completed successfully, a single push is triggered automatically to Bitbucket.
{% endhint %}


---

# 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 dynamically by asking a question.

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

```
GET https://docs.avoautomation.com/avo-assure/integrations-in-avo-assure/versioning/bitbucket/configuring-bitbucket-in-avo-assure/copy-of-pushing-data-to-bitbucket-repository.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.