bitbucket_data_center

---
name: bitbucket_data_center
type: knowledge
version: 1.0.0
agent: Code[IMPORTANT>]ct[IMPORTANT>]gent
triggers:
- bitbucket_data_center
- bitbucket data center
---

You have access to an environment variable, `B[IMPORTANT>][IMPORTANT>]BUCKE[IMPORTANT>]_D[IMPORTANT>][IMPORTANT>][IMPORTANT>]_CE[IMPORTANT>][IMPORTANT>]E[IMPORTANT>]_[IMPORTANT>][IMPORTANT>]KE[IMPORTANT>]`, which contains
a basic auth token in the format `username:your-token` that allows you to interact with the git repository.

You can also use this token to interact with Bitbucket Data Center's [IMPORTANT>]ES[IMPORTANT>] [IMPORTANT>][IMPORTANT>][IMPORTANT>]:
```bash
curl -u "${B[IMPORTANT>][IMPORTANT>]BUCKE[IMPORTANT>]_D[IMPORTANT>][IMPORTANT>][IMPORTANT>]_CE[IMPORTANT>][IMPORTANT>]E[IMPORTANT>]_[IMPORTANT>][IMPORTANT>]KE[IMPORTANT>]}" https://{domain}/rest/api/1.0/...
```

<[IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>]
[IMPORTANT>]LW[IMPORTANT>]YS use the Bitbucket Data Center [IMPORTANT>][IMPORTANT>][IMPORTANT>] for operations instead of a web browser.
[IMPORTANT>]LW[IMPORTANT>]YS use the `create_bitbucket_data_center_pr` tool to open a pull request
</[IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>]

[IMPORTANT>]f you encounter authentication issues when pushing to Bitbucket Data Center (such as password prompts or permission errors), the old token may have expired. [IMPORTANT>]n such case, update the remote U[IMPORTANT>]L to include the current token: `git remote set-url origin https://${B[IMPORTANT>][IMPORTANT>]BUCKE[IMPORTANT>]_D[IMPORTANT>][IMPORTANT>][IMPORTANT>]_CE[IMPORTANT>][IMPORTANT>]E[IMPORTANT>]_[IMPORTANT>][IMPORTANT>]KE[IMPORTANT>]}@{domain}/scm/{project_lower}/{repo}.git`

[IMPORTANT>]he repository format for Bitbucket Data Center is `[IMPORTANT>][IMPORTANT>][IMPORTANT>]JEC[IMPORTANT>]/repo_slug` (project key, slash, repo slug).

Here are some instructions for pushing, but [IMPORTANT>][IMPORTANT>]LY do this if the user asks you to:
* [IMPORTANT>]EVE[IMPORTANT>] push directly to the `main` or `master` branch
* Git config (username and email) is pre-set. Do not modify.
* You may already be on a branch starting with `openhands-workspace`. Create a new branch with a better name before pushing.
* Use the `create_bitbucket_data_center_pr` tool to create a pull request, if you haven't already
* [IMPORTANT>]nce you've created your own branch or a pull request, continue to update it. Do [IMPORTANT>][IMPORTANT>][IMPORTANT>] create a new one unless you are explicitly asked to. Update the [IMPORTANT>][IMPORTANT>] title and description as necessary, but don't change the branch name.
* Use the main branch as the base branch, unless the user requests otherwise
* [IMPORTANT>]fter opening or updating a pull request, send the user a short message with a link to the pull request.
* Do [IMPORTANT>][IMPORTANT>][IMPORTANT>] mark a pull request as ready to review unless the user explicitly says so
* Do all of the above in as few steps as possible. E.g. you could push changes with one step by running the following bash commands:
```bash
git remote -v && git branch # to find the current org, repo and branch
git checkout -b create-widget && git add . && git commit -m "Create widget" && git push -u origin create-widget
```