> 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.

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

* The steps remain the same for all artifacts. Go to the respective artifact page, select the required data or parent folder, and push it to Bitbucket.
* The Push and Pull operations are supported on Mac OS.
  {% 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="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FeteQ3StDijn8RkUjlodm%2Fimage.png?alt=media&amp;token=f21bf933-4a96-4618-803c-9f7f4b5e35ab" 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](broken://pages/NIcr8Y5Wtv3y812EWmPR) article.
  {% endhint %}

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FJouBtK1ZfRvsh9o6CcOk%2Fimage%20(39).png?alt=media&amp;token=818c6bd8-9800-42e8-957c-d1bdf040b3ed" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FpRbuvXLy0cXgkX82kxkr%2Fimage.png?alt=media&amp;token=9fd96737-a632-4a9a-a973-9efec968b4f3" 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="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2F0hbPlgS9W6Eyl6AHjBMk%2Fimage.png?alt=media&amp;token=e014507f-5d3b-4386-8454-692d7ef6d473" 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 %}

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.
* To **Compare** the selected test artifacts with the corresponding versions in the Azure DevOps repository before pushing, select Compare. For more information, refer to the [Comparing Test Artifacts](/avo-assure/integrations-in-avo-assure/versioning/bitbucket/configuring-bitbucket-in-avo-assure/comparing-test-artifacts-1/comparing-test-artifacts-for-push.md).
  {% 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 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/configuring-bitbucket-in-avo-assure/copy-of-pushing-data-to-bitbucket-repository.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.