Connect Bitbucket
Temps connects to Bitbucket Cloud (bitbucket.org). You can authenticate with a Repository or Workspace Access Token (recommended) or an App Password. Once connected, Temps registers the webhook for you and can post preview comments on pull requests. Start from Connect a Git Provider if you haven't opened the Git Providers page yet.
Access token (recommended)
- In Bitbucket, create a Repository Access Token (Repository settings → Access tokens) or a Workspace Access Token (Workspace settings → Access tokens) with Repositories: Read, plus Webhooks: Read and write for push-triggered deploys and Pull requests: Write for preview comments.
- Copy the token.
- In Temps, on the Add Git Provider screen choose Bitbucket → Access Token, paste the token into the Token field, and click Connect.
App password
- Create an app password at bitbucket.org/account/settings/app-passwords with Repositories: Read, Webhooks: Read and write, and Pull requests: Write.
- In Temps choose Bitbucket → App Password, enter your Atlassian username and the app password, and click Connect.
Temps registers the Bitbucket webhook automatically when you link a repository to a project. If registration fails (for example, the token lacks the webhook scope), the connection still succeeds and the webhook URL is shown so you can add it manually.
Bitbucket Data Center
Running Bitbucket Data Center / Server (self-hosted)? It uses a different API and is not supported directly — connect it through Other Git Providers instead.
Once connected, confirm the status shows Active and continue with Confirm the connection.