Merge branch 'main' into PORT-trigger-gemini

Author: PeyGis

docs/build-your-software-catalog/sync-data-to-catalog/git/azure-devops/advanced.md

@@ -34,6 +34,10 @@ The following advanced configuration parameters are available and can be added t
 
 <TabItem label="Spec path" value="specPath">
 
+:::warning Deprecated parameter
+  The `specPath` parameter is deprecated. We recommend using the [file kind](https://docs.port.io/build-your-software-catalog/sync-data-to-catalog/git/azure-devops/#ingest-files-from-your-repositories) for GitOps instead, which provides more flexible file ingestion capabilities.
+:::
+
 The `specPath` parameter specifies a list of `string` or a single value `string` that Port's Azure Devops app will search for `port.yml` files in.
 
 - **Default value**: `port.yml`
@@ -72,12 +76,16 @@ The `createMissingRelatedEntities` parameter is used to enable the creation of m
 
 <TabItem value="branch" label="Branch">
 
+:::warning Deprecated parameter
+The `branch` parameter is deprecated. We recommend using the [file kind](https://docs.port.io/build-your-software-catalog/sync-data-to-catalog/git/azure-devops/#ingest-files-from-your-repositories) for GitOps instead, which provides more flexible file ingestion capabilities.
+:::
+
 The Azure Devops integration listens to real-time events from the branch specified in the `branch` field which is set to `main` by default. This is configurable and you can set the `branch` parameter to the branch you want to listen to events from.
 
 - **Default value**: `main` (default to the branch specified in the `branch` field.)
 - **Use case**: `develop` if you want to listen to events from the `develop` branch of the repository.
 
-:::note Use Default Branch
+:::info Use default branch
 
 If you want to listen to events from the default branch of the repository, you can set the `useDefaultBranch` parameter to `true`.
 

docs/build-your-software-catalog/sync-data-to-catalog/git/github-ocean/examples/example-repository-collaborators/_github_exporter_example_repository_collaborator_port_app_config.mdx

@@ -8,6 +8,7 @@ resources:
   - kind: repository
     selector:
       query: "true" # JQ boolean query. If evaluated to false - skip syncing the object.
+      include: ["collaborators"] # Include collaborators as a relationship
     port:
       entity:
         mappings:

docs/build-your-software-catalog/sync-data-to-catalog/git/github-ocean/examples/example-repository-teams/_github_exporter_example_repository_with_teams_port_app_config.mdx

@@ -25,7 +25,7 @@ resources:
   - kind: repository
     selector:
       query: "true" # JQ boolean query. If evaluated to false - skip syncing the object.
-      include: "teams" # Boolean flag to indicate whether to include the repository teams.
+      include: ["teams"] # List of relationship types to include. Can include multiple types like ["teams", "collaborators"].
     port:
       entity:
         mappings:

docs/build-your-software-catalog/sync-data-to-catalog/git/github-ocean/examples/examples.md

@@ -199,6 +199,50 @@ You can use the following Port blueprint definitions and `port-app-config.yml`:
 <PortRepositoryTeamMappingAppConfig/>
 
 
+## Map repositories with multiple relationships
+
+You can now include multiple relationship types in a single repository configuration. For example, to include both teams and collaborators:
+
+```yaml showLineNumbers
+- kind: repository
+  selector:
+    query: "true"
+    include: ["teams", "collaborators"] # Include both teams and collaborators
+  port:
+    entity:
+      mappings:
+        identifier: .name
+        title: .name
+        blueprint: '"githubRepository"'
+        properties:
+          readme: file://README.md
+          url: .html_url
+          defaultBranch: .default_branch
+        relations:
+          githubTeams: "[.__teams[].id | tostring]"
+          githubCollaborators: "[.__collaborators[].login]"
+```
+
+:::caution Performance consideration
+While you can include multiple relationship types in a single configuration, this may impact resync performance for large repositories. For optimal performance, consider separating into multiple repository blocks:
+
+```yaml showLineNumbers
+# Separate blocks for better performance
+- kind: repository
+  selector:
+    query: "true"
+    include: ["teams"]
+  # ... rest of configuration
+
+- kind: repository  
+  selector:
+    query: "true"
+    include: ["collaborators"]
+  # ... rest of configuration
+```
+:::
+
+
 ## Map teams and team members
 
 The following shows how we can map teams and team members using the "members" selector.