port-labs · lordsarcastic · Jun 23, 2025 · Jun 24, 2025 · Jun 24, 2025 · Jun 25, 2025
diff --git a/docs/build-your-software-catalog/custom-integration/gitops.md b/docs/build-your-software-catalog/custom-integration/gitops.md
@@ -13,5 +13,5 @@ To use Gitops with Port, head over to your desired Git provider:
 
 - [GitHub](/build-your-software-catalog/sync-data-to-catalog/git/github/gitops)
 - [GitLab](/build-your-software-catalog/sync-data-to-catalog/git/gitlab/gitops)
-- [Bitbucket](/build-your-software-catalog/sync-data-to-catalog/git/bitbucket/gitops)
+- [Bitbucket](/build-your-software-catalog/sync-data-to-catalog/git/bitbucket/bitbucket-cloud/gitops)
 - [Azure DevOps](/build-your-software-catalog/sync-data-to-catalog/git/azure-devops/gitops)
diff --git a/...our-software-catalog/custom-integration/webhook/examples/bitbucket-server/_category_.json b/...our-software-catalog/custom-integration/webhook/examples/bitbucket-server/_category_.json
diff --git a/docs/build-your-software-catalog/sync-data-to-catalog/git/bitbucket/_category_.json b/docs/build-your-software-catalog/sync-data-to-catalog/git/bitbucket/_category_.json
@@ -1,4 +1,4 @@
 {
-  "label": "Bitbucket (deprecated)",
-  "position": 2
-}
+  "label": "Bitbucket",
+  "position": 3
+}
diff --git a/...rter_example_monorepo_port_app_config.mdx → ...rter_example_monorepo_port_app_config.mdx b/...rter_example_monorepo_port_app_config.mdx → ...rter_example_monorepo_port_app_config.mdx
diff --git a/...cket_exporter_example_port_app_config.mdx → ...cket_exporter_example_port_app_config.mdx b/...cket_exporter_example_port_app_config.mdx → ...cket_exporter_example_port_app_config.mdx
diff --git a/...porter_example_pull_request_blueprint.mdx → ...porter_example_pull_request_blueprint.mdx b/...porter_example_pull_request_blueprint.mdx → ...porter_example_pull_request_blueprint.mdx
diff --git a/...exporter_example_repository_blueprint.mdx → ...exporter_example_repository_blueprint.mdx b/...exporter_example_repository_blueprint.mdx → ...exporter_example_repository_blueprint.mdx
diff --git a/...itbucket_exporter_supported_resources.mdx → ...itbucket_exporter_supported_resources.mdx b/...itbucket_exporter_supported_resources.mdx → ...itbucket_exporter_supported_resources.mdx
diff --git a/...ld-your-software-catalog/sync-data-to-catalog/git/bitbucket/bitbucket-app/_category_.json b/...ld-your-software-catalog/sync-data-to-catalog/git/bitbucket/bitbucket-app/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Bitbucket (deprecated)",
+  "position": 2
+}
diff --git a/...data-to-catalog/git/bitbucket/advanced.md → ...g/git/bitbucket/bitbucket-app/advanced.md b/...data-to-catalog/git/bitbucket/advanced.md → ...g/git/bitbucket/bitbucket-app/advanced.md
@@ -4,7 +4,7 @@ sidebar_position: 4
 
 import Tabs from "@theme/Tabs"
 import TabItem from "@theme/TabItem"
-import DeleteDependents from '../../../../generalTemplates/\_delete_dependents_git_explanation_template.md'
+import DeleteDependents from '../../../../../generalTemplates/\_delete_dependents_git_explanation_template.md'
 
 # Advanced
 
@@ -57,4 +57,4 @@ The `createMissingRelatedEntities` parameter is used to enable the creation of m
 
 </Tabs>
 
-All of the advanced configurations listed below can be added to the [`port-app-config.yml`](./bitbucket.md#port-app-configyml-file) file.
+All of the advanced configurations listed above can be added to the [`port-app-config.yml`](./bitbucket-app.md#port-app-configyml-file) file.
diff --git a/...ata-to-catalog/git/bitbucket/bitbucket.md → .../bitbucket/bitbucket-app/bitbucket-app.md b/...ata-to-catalog/git/bitbucket/bitbucket.md → .../bitbucket/bitbucket-app/bitbucket-app.md
@@ -3,19 +3,19 @@ import TabItem from "@theme/TabItem"
 import BitbucketResources from './\_bitbucket_exporter_supported_resources.mdx'
 
 
-# Bitbucket
+# Bitbucket (App)
 
-Port's Bitbucket integration allows you to model Bitbucket resources in your software catalog and ingest data into them.
+Port's Bitbucket (App) integration allows you to model Bitbucket resources in your software catalog and ingest data into them.
 
 :::warning Deprecation Notice
 This app will be deprecated in the future and support for the app will be discontinued soon.
 
-To integrate Port with Bitbucket Cloud, we recommend using the [Bitbucket Cloud integration](/build-your-software-catalog/sync-data-to-catalog/git/bitbucket-cloud/).
+To integrate Port with Bitbucket Cloud, we recommend using the [Bitbucket Cloud integration](/build-your-software-catalog/sync-data-to-catalog/git/bitbucket/bitbucket-cloud/).
 :::
 
 :::info Bitbucket Server (Self-Hosted)
 This documentation covers Port's integration with **Bitbucket Cloud**. 
-For information about integrating with Bitbucket Server (Self-Hosted), please refer to the [Bitbucket Server integration documentation](/build-your-software-catalog/custom-integration/webhook/examples/bitbucket-server/bitbucket-server.md).
+For information about integrating with Bitbucket Server (Self-Hosted), please refer to the [Bitbucket Server integration documentation](/build-your-software-catalog/sync-data-to-catalog/git/bitbucket/bitbucket-server/bitbucket-server.md).
 :::
 
 

diff --git a/...data-to-catalog/git/bitbucket/examples.md → ...g/git/bitbucket/bitbucket-app/examples.md b/...data-to-catalog/git/bitbucket/examples.md → ...g/git/bitbucket/bitbucket-app/examples.md
@@ -22,7 +22,7 @@ In the following example you will ingest your Bitbucket repositories, their READ
 
 :::tip
 
-- Refer to the [setup](bitbucket.md#setup) section to learn more about the `port-app-config.yml` setup process;
+- Refer to the [setup](bitbucket-app.md#setup) section to learn more about the `port-app-config.yml` setup process;
 - We leverage [JQ JSON processor](https://stedolan.github.io/jq/manual/) to map and transform Bitbucket objects to Port Entities;
 - Click [Here](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-repositories/#api-repositories-workspace-repo-slug-get) for the Bitbucket repository object structure.
 - Click [Here](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-pullrequests/#api-repositories-workspace-repo-slug-pullrequests-pull-request-id-get) for the Bitbucket pull request object structure.
@@ -41,7 +41,7 @@ In the following example you will ingest your Bitbucket repositories and their f
 
 :::tip
 
-- Refer to the [setup](bitbucket.md#setup) section to learn more about the `port-app-config.yml` setup process;
+- Refer to the [setup](bitbucket-app.md#setup) section to learn more about the `port-app-config.yml` setup process;
 - We leverage [JQ JSON processor](https://stedolan.github.io/jq/manual/) to map and transform GitHub objects to Port Entities;
 - Click [Here](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-repositories/#api-repositories-workspace-repo-slug-get) for the Bitbucket repository object structure.
 - Click [Here](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-source/#api-repositories-workspace-repo-slug-src-commit-path-get) for the Bitbucket folder object structure.

diff --git a/...it/bitbucket-cloud/gitops/_category_.json → ...cket/bitbucket-app/gitops/_category_.json b/...it/bitbucket-cloud/gitops/_category_.json → ...cket/bitbucket-app/gitops/_category_.json
diff --git a/...to-catalog/git/bitbucket/gitops/gitops.md → .../bitbucket/bitbucket-app/gitops/gitops.md b/...to-catalog/git/bitbucket/gitops/gitops.md → .../bitbucket/bitbucket-app/gitops/gitops.md
@@ -4,19 +4,19 @@ sidebar_position: 3
 
 import Tabs from "@theme/Tabs"
 import TabItem from "@theme/TabItem"
-import PortYmlStructure from '../../\_port_yml_gitops_structure_template.md'
-import BasicFileProperties from '../../\_basic_file_properties_template.md'
-import RelativeFileProperties from '../../\_relative_file_properties_template.md'
-import GitOpsPushEvent from '../../\_git_gitops_push_events_explanation.mdx'
-import PortYmlIngestionPattern from '../../\_port_yml_ingestion_pattern_template.md'
+import PortYmlStructure from '../../../\_port_yml_gitops_structure_template.md'
+import BasicFileProperties from '../../../\_basic_file_properties_template.md'
+import RelativeFileProperties from '../../../\_relative_file_properties_template.md'
+import GitOpsPushEvent from '../../../\_git_gitops_push_events_explanation.mdx'
+import PortYmlIngestionPattern from '../../../\_port_yml_ingestion_pattern_template.md'
 
 # GitOps
 
 Port's Bitbucket integration makes it possible to manage Port entities with a GitOps approach, making your code repositories into the source of truth for the various infrastructure assets you want to manage.
 
 :::info Bitbucket Server (Self-Hosted)
 This documentation covers GitOps for **Bitbucket Cloud**. 
-For information about GitOps with Bitbucket Server (Self-Hosted), please refer to the [Bitbucket Server GitOps documentation](/build-your-software-catalog/custom-integration/webhook/examples/bitbucket-server/gitops.md).
+For information about GitOps with Bitbucket Server (Self-Hosted), please refer to the [Bitbucket Server GitOps documentation](/build-your-software-catalog/sync-data-to-catalog/git/bitbucket/bitbucket-server/webhook/gitops.md).
 :::
 
 
@@ -30,7 +30,7 @@ For information about GitOps with Bitbucket Server (Self-Hosted), please refer t
 
 To manage entities using GitOps, you will need to add a `port.yml` file to the **default branch** (usually `main`) of your repository.
 
-Note that the `port.yml` file is not the same as the [`port-app-config.yml` file](/build-your-software-catalog/sync-data-to-catalog/git/bitbucket/#port-app-configyml-file) used to configure the BitBucket integration, and does not replace it.
+Note that the `port.yml` file is not the same as the [`port-app-config.yml` file](/build-your-software-catalog/sync-data-to-catalog/git/bitbucket/bitbucket-app/#port-app-configyml-file) used to configure the BitBucket integration, and does not replace it.
 
 The `port.yml` file can specify one or more Port entities that will be ingested to Port, and any change made to the `port.yml` file will also be reflected inside Port.
 

diff --git a/...cket_cloud_one_time_docker_parameters.mdx → ...cket_cloud_one_time_docker_parameters.mdx b/...cket_cloud_one_time_docker_parameters.mdx → ...cket_cloud_one_time_docker_parameters.mdx
diff --git a/...et_integration_example_file_blueprint.mdx → ...et_integration_example_file_blueprint.mdx b/...et_integration_example_file_blueprint.mdx → ...et_integration_example_file_blueprint.mdx
diff --git a/...egration_example_file_port_app_config.mdx → ...egration_example_file_port_app_config.mdx b/...egration_example_file_port_app_config.mdx → ...egration_example_file_port_app_config.mdx
diff --git a/...tion_example_monorepo_port_app_config.mdx → ...tion_example_monorepo_port_app_config.mdx b/...tion_example_monorepo_port_app_config.mdx → ...tion_example_monorepo_port_app_config.mdx
diff --git a/...t_integration_example_port_app_config.mdx → ...t_integration_example_port_app_config.mdx b/...t_integration_example_port_app_config.mdx → ...t_integration_example_port_app_config.mdx
diff --git a/...integration_example_project_blueprint.mdx → ...integration_example_project_blueprint.mdx b/...integration_example_project_blueprint.mdx → ...integration_example_project_blueprint.mdx
diff --git a/...ration_example_pull_request_blueprint.mdx → ...ration_example_pull_request_blueprint.mdx b/...ration_example_pull_request_blueprint.mdx → ...ration_example_pull_request_blueprint.mdx
diff --git a/...egration_example_repository_blueprint.mdx → ...egration_example_repository_blueprint.mdx b/...egration_example_repository_blueprint.mdx → ...egration_example_repository_blueprint.mdx
diff --git a/...ucket_integration_supported_resources.mdx → ...ucket_integration_supported_resources.mdx b/...ucket_integration_supported_resources.mdx → ...ucket_integration_supported_resources.mdx
diff --git a/...talog/git/bitbucket-cloud/_category_.json → ...bitbucket/bitbucket-cloud/_category_.json b/...talog/git/bitbucket-cloud/_category_.json → ...bitbucket/bitbucket-cloud/_category_.json
diff --git a/...o-catalog/git/bitbucket-cloud/advanced.md → ...git/bitbucket/bitbucket-cloud/advanced.md b/...o-catalog/git/bitbucket-cloud/advanced.md → ...git/bitbucket/bitbucket-cloud/advanced.md
@@ -4,7 +4,7 @@ sidebar_position: 4
 
 import Tabs from "@theme/Tabs"
 import TabItem from "@theme/TabItem"
-import DeleteDependents from '../../../../generalTemplates/\_delete_dependents_git_explanation_template.md'
+import DeleteDependents from '../../../../../generalTemplates/\_delete_dependents_git_explanation_template.md'
 
 # Advanced
 

diff --git a/...og/git/bitbucket-cloud/bitbucket-cloud.md → ...bucket/bitbucket-cloud/bitbucket-cloud.md b/...og/git/bitbucket-cloud/bitbucket-cloud.md → ...bucket/bitbucket-cloud/bitbucket-cloud.md
@@ -9,7 +9,7 @@ Port's Bitbucket integration allows you to model Bitbucket cloud resources in yo
 
 :::info Bitbucket Server (Self-Hosted)
 This documentation covers Port's integration with **Bitbucket Cloud**. 
-For information about integrating with Bitbucket Server (Self-Hosted), please refer to the [Bitbucket Server integration documentation](/build-your-software-catalog/custom-integration/webhook/examples/bitbucket-server/bitbucket-server.md).
+For information about integrating with Bitbucket Server (Self-Hosted), please refer to the [Bitbucket Server integration documentation](/build-your-software-catalog/sync-data-to-catalog/git/bitbucket/bitbucket-server/bitbucket-server.md).
 :::
 
 

diff --git a/...o-catalog/git/bitbucket-cloud/examples.md → ...git/bitbucket/bitbucket-cloud/examples.md b/...o-catalog/git/bitbucket-cloud/examples.md → ...git/bitbucket/bitbucket-cloud/examples.md
diff --git a/...alog/git/bitbucket/gitops/_category_.json → ...et/bitbucket-cloud/gitops/_category_.json b/...alog/git/bitbucket/gitops/_category_.json → ...et/bitbucket-cloud/gitops/_category_.json
diff --git a/...alog/git/bitbucket-cloud/gitops/gitops.md → ...itbucket/bitbucket-cloud/gitops/gitops.md b/...alog/git/bitbucket-cloud/gitops/gitops.md → ...itbucket/bitbucket-cloud/gitops/gitops.md
@@ -4,18 +4,18 @@ sidebar_position: 3
 
 import Tabs from "@theme/Tabs"
 import TabItem from "@theme/TabItem"
-import PortYmlStructure from '../../\_port_yml_gitops_structure_template.md'
-import BasicFileProperties from '../../\_basic_file_properties_template.md'
-import RelativeFileProperties from '../../\_relative_file_properties_template.md'
-import PortYmlIngestionPattern from '../../\_port_yml_ingestion_pattern_template.md'
+import PortYmlStructure from '../../../\_port_yml_gitops_structure_template.md'
+import BasicFileProperties from '../../../\_basic_file_properties_template.md'
+import RelativeFileProperties from '../../../\_relative_file_properties_template.md'
+import PortYmlIngestionPattern from '../../../\_port_yml_ingestion_pattern_template.md'
 
 # GitOps
 
 Port's Bitbucket integration makes it possible to manage Port entities with a GitOps approach, making your code repositories into the source of truth for the various infrastructure assets you want to manage.
 
 :::info Bitbucket Server (Self-Hosted)
 This documentation covers GitOps for **Bitbucket Cloud**. 
-For information about GitOps with Bitbucket Server (Self-Hosted), please refer to the [Bitbucket Server GitOps documentation](/build-your-software-catalog/custom-integration/webhook/examples/bitbucket-server/gitops.md).
+For information about GitOps with Bitbucket Server (Self-Hosted), please refer to the [Bitbucket Server GitOps documentation](/build-your-software-catalog/sync-data-to-catalog/git/bitbucket/bitbucket-server/webhook/gitops.md).
 :::
 
 
@@ -29,7 +29,7 @@ For information about GitOps with Bitbucket Server (Self-Hosted), please refer t
 
 To manage entities using GitOps, you will need to add a `port.yml` file to the **default branch** (usually `main`) of your repository.
 
-Note that the `port.yml` file is not the same as the [`port-app-config.yml` file](/build-your-software-catalog/sync-data-to-catalog/git/bitbucket/#port-app-configyml-file) used to configure the BitBucket integration, and does not replace it.
+Note that the `port.yml` file is not the same as the [`port-app-config.yml` file](/build-your-software-catalog/sync-data-to-catalog/git/bitbucket/bitbucket-cloud/#port-app-configyml-file) used to configure the BitBucket integration, and does not replace it.
 
 The `port.yml` file can specify one or more Port entities that will be ingested to Port, and any change made to the `port.yml` file will also be reflected inside Port.
 

diff --git a/...talog/git/bitbucket-cloud/installation.md → ...bitbucket/bitbucket-cloud/installation.md b/...talog/git/bitbucket-cloud/installation.md → ...bitbucket/bitbucket-cloud/installation.md
@@ -4,11 +4,11 @@ sidebar_position: 1
 
 import Tabs from "@theme/Tabs"
 import TabItem from "@theme/TabItem"
-import AzurePremise from "../../templates/\_ocean_azure_premise.mdx"
-import Prerequisites from "../../templates/\_ocean_helm_prerequisites_block.mdx"
-import HelmParameters from "../../templates/\_ocean-advanced-parameters-helm.mdx"
+import AzurePremise from "../../../templates/\_ocean_azure_premise.mdx"
+import Prerequisites from "../../../templates/\_ocean_helm_prerequisites_block.mdx"
+import HelmParameters from "../../../templates/\_ocean-advanced-parameters-helm.mdx"
 import DockerParameters from "./\_bitbucket_cloud_one_time_docker_parameters.mdx"
-import AdvancedConfig from '../../../../generalTemplates/_ocean_advanced_configuration_note.md'
+import AdvancedConfig from '../../../../../generalTemplates/_ocean_advanced_configuration_note.md'
 import PortApiRegionTip from "/docs/generalTemplates/_port_region_parameter_explanation_template.md"
 import OceanSaasInstallation from "/docs/build-your-software-catalog/sync-data-to-catalog/templates/_ocean_saas_installation.mdx"
 import OceanRealtimeInstallation from "/docs/build-your-software-catalog/sync-data-to-catalog/templates/_ocean_realtime_installation.mdx"