For the complete documentation index, see llms.txt. This page is also available as Markdown.
Configuring Bitbucket Token Authentication and Email Support
Introduction
Bitbucket is deprecating App Password authentication effective June 9, 2026. To ensure uninterrupted connectivity and support for Bitbucket API operations, AutoRABIT supports Token-based authentication and provides an Email Address field for Bitbucket credentials.
This guide explains how to configure and update Bitbucket credentials in AutoRABIT.
Prerequisites
Before proceeding, ensure that:
You have access to your Bitbucket account.
A Bitbucket App Token has been generated.
You know the email address associated with your Bitbucket account.
When Is an Email Address Required?
An email address is required for Bitbucket API-based operations such as:
Pull Request Creation
Other Bitbucket REST API operations
The email address is not required for Git operations such as:
Clone
Fetch
Push
Configuring a New Bitbucket Credential
New UI
Navigate to Settings → Credentials.
Click Create Credential.
Select Bitbucket as the repository type.
Enter the following information:
Username
Token
Email Address (Optional)
Click Save.
Updating an Existing Bitbucket Credential
Navigate to Settings → Credentials.
Locate the Bitbucket credential.
Click Edit.
Enter or update the Email Address field.
Save the changes.
Repository Registration
When registering a Bitbucket repository:
Select the Bitbucket credential.
Verify that the credential contains:
Username
Token
Email Address (recommended)
Complete repository registration.
Updating Version Control Mappings (New UI)
Navigate to My Profile → Version Control Mappings.
Select the Bitbucket credential.
Verify the Email Address is configured.
Save the mapping.
Best Practices
Migrate from App Passwords to Tokens before June 9, 2026.
Configure an Email Address for all Bitbucket credentials used for Pull Request workflows.
Periodically review and update repository credentials.
