Merge branch 'main' into add-swagger-link-to-pages

Author: sivanel97

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

@@ -45,4 +45,38 @@ To do so, we will use the `file://` prefix with the path of the file to tell the
             url: .remoteUrl
             // highlight-next-line
             readme: file://README.md
-```
+```
+
+## Link pipelines to repositories via selector
+You can configure your selector to include repository information in the pipeline entity mapping.
+This allows you to create a direct relationship between a pipeline and its source repository.
+
+```yaml showLineNumbers
+- kind: pipeline
+  selector:
+    query: 'true'
+    # highlight-next-line
+    includeRepo: 'true'
+  port:
+    entity:
+      mappings:
+        identifier: .id | tostring
+        title: .name
+        blueprint: '"azureDevOpsPipeline"'
+        properties:
+          url: .url
+          revision: .revision
+          folder: .folder
+        relations:
+          project: .__projectId | gsub(" "; "")
+          repository: >-
+            if .__repository
+            then .__repository.project.name + "/" + .__repository.name | gsub(" "; "")
+            else null
+            end
+```
+:::tip Recommendation
+Use this only when necessary, as including repository data requires an extra API call per pipeline, which increases the number of requests made and can impact your Azure DevOps API rate limits.
+
+If you don’t require repo-level linkage, it’s more efficient to relate pipelines → projects instead.
+:::

docs/guides/all/visualize-service-k8s-runtime.md

@@ -106,32 +106,32 @@ We achieved this by adding a [mapping definition](https://github.com/port-labs/t
         apiVersion: apps/v1
         kind: Deployment
         metadata:
-        name: awesomeapp
-        labels:
+          name: awesomeapp
+          labels:
             app: nginx
             portWorkload: AwesomeWorkload
         spec:
-        replicas: 2
-        selector:
+          replicas: 2
+          selector:
             matchLabels:
-            app: nginx
-        template:
+              app: nginx
+          template:
             metadata:
-            labels:
+              labels:
                 app: nginx
             spec:
-            containers:
+              containers:
                 - name: nginx
                   image: nginx:1.14.2
                   resources:
-                      limits:
+                    limits:
                       cpu: "200m"
                       memory: "256Mi"
-                      requests:
-                        cpu: "100m"
-                        memory: "128Mi"
+                    requests:
+                      cpu: "100m"
+                      memory: "128Mi"
                   ports:
-                      - containerPort: 80
+                    - containerPort: 80
     ```
 
     </details>