Skip to content

Updated the Bitbucket integration information #1438

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
maryiaCodefresh wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Updated the Bitbucket integration information #1438

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a8bc14f
Updated OAuth2 Bitbucket integration information
maryiaCodefresh Aug 19, 2026
83c66d4
Updated the Bitbucket integration information in git-providers.md
maryiaCodefresh Aug 19, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions _docs/integrations/git-providers.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -237,14 +237,11 @@ For example if you already have a `token` on a resource call `git-credentials` y

## Bitbucket

For the **OAuth2 method** you only need to enter a name for your connection and click *Save*. Then accept the permissions dialog. This is the easiest and recommended way to integrate Bitbucket. Notice that if
you used Bitbucket when you [created your Codefresh account]({{site.baseurl}}/docs/administration/account-user-management/create-codefresh-account/), this integration is already setup for you.

>**WARNING!**
Bitbucket **App passwords** will be deprecated on **June 9th 2026**. For details, see [the official announcement from Bitbucket](https://www.atlassian.com/blog/bitbucket/bitbucket-cloud-transitions-to-api-tokens-enhancing-security-with-app-password-deprecation).<br />
If you already use an App password for your Bitbucket integration in Codefresh, we recommend switching to the new **API token** method described below.

For the **API token** method you need:
The **API token method** is the recommended way to integrate Bitbucket. To set it up, you’ll need:

* A friendly name for the Git context (It can be anything you want.)
* The email associated with your Bitbucket account
Expand Down Expand Up @@ -297,6 +294,9 @@ now save the Git integration.

If enabled in your account you can setup [Pipeline definition restrictions]({{site.baseurl}}/docs/administration/account-user-management/access-control/#pipeline-definition-restrictions) by expanding the *YAML Options* segment.

For the **OAuth2 method** you need to enter a name for your connection and click *Save*. Then accept the permissions dialog.
For customers with high Bitbucket API usage, we recommend using the **API token method** instead of OAuth2.

## Azure DevOps

For Azure you need to create a [personal access token](https://docs.microsoft.com/en-us/azure/devops/integrate/get-started/authentication/pats?view=azure-devops){:target="\_blank"}. Sign in your Azure DevOps account and click on your profile icon on the top right corner. Then select *Security*:
Expand Down