From a8bc14f580821a4d3a1b78938e98d55671ec2459 Mon Sep 17 00:00:00 2001
From: maryiaCodefresh <146828154+maryiaCodefresh@users.noreply.github.com>
Date: Wed, 19 Aug 2026 15:40:07 +0300
Subject: [PATCH 1/2] Updated OAuth2 Bitbucket integration information
Moved the OAuth2 Bitbucket integration to the end of the section to highlight the token integration
Removed incorrect information stating this is the recommended approach, it no longer reflects our team's decision: https://linear.app/octopus/issue/CF-1896/reviewing-bitbucket-api-rate-limit-consumtion-by-customers#comment-70e49c4c
---
_docs/integrations/git-providers.md | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/_docs/integrations/git-providers.md b/_docs/integrations/git-providers.md
index 20c3cb163..d40ba4085 100644
--- a/_docs/integrations/git-providers.md
+++ b/_docs/integrations/git-providers.md
@@ -237,9 +237,6 @@ 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).
If you already use an App password for your Bitbucket integration in Codefresh, we recommend switching to the new **API token** method described below.
@@ -297,6 +294,8 @@ 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 only need to enter a name for your connection and click *Save*. Then accept the permissions dialog.
+
## 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*:
From 83c66d475f1fc3ba0a7296b73d1a4b1dc6cca5ac Mon Sep 17 00:00:00 2001
From: maryiaCodefresh <146828154+maryiaCodefresh@users.noreply.github.com>
Date: Wed, 19 Aug 2026 16:17:19 +0300
Subject: [PATCH 2/2] Updated the Bitbucket integration information in
git-providers.md
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Highlighted the API token method as the recommended option
Added a note to the OAuth2 method that we don’t recommend it for customers with high Bitbucket API usage
---
_docs/integrations/git-providers.md | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/_docs/integrations/git-providers.md b/_docs/integrations/git-providers.md
index d40ba4085..89b9059b8 100644
--- a/_docs/integrations/git-providers.md
+++ b/_docs/integrations/git-providers.md
@@ -241,7 +241,7 @@ For example if you already have a `token` on a resource call `git-credentials` y
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).
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
@@ -294,7 +294,8 @@ 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 only need to enter a name for your connection and click *Save*. Then accept the permissions dialog.
+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