fix: handle pr reviews

Author: emekanwaoma

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

@@ -22,7 +22,7 @@ Here's what you can do with the GitHub integration:
 
 ### Multi-organization support
 
-The GitHub integration supports syncing data from multiple GitHub organizations starting from **version 3.0.0-beta**. You can configure which organizations to sync using a single-org `githubOrganization`, or by listing organizations in your Port mapping (`organizations`).
+The GitHub integration supports syncing data from multiple GitHub organizations starting from **version 3.0.0-beta**. You can configure which organizations to sync using a single-org `githubOrganization`, or by listing organizations in your port mapping (`organizations`).
 
 <details>
 <summary><b>Mapping multi organizations (Click to expand)</b></summary>
@@ -41,11 +41,10 @@ organizations:
 
 :::caution Authentication and configuration requirements:
 - **With classic PAT**:
-  - Specify organizations in PortMapping: `organizations: ["org1", "org2", "org3"]`
-- **With GitHub App**: Specify exactly one organization: `githubOrganization: "my-org"`
-- **With Fine-grained PAT**: Specify exactly one organization: `githubOrganization: "my-org"`
+  - Specify organizations in port mapping: `organizations: ["org1", "org2", "org3"]`
+- **With GitHub App or Fine-grained PAT**: Specify exactly one organization by setting the `githubOrganization` in the environment variables: `githubOrganization: "my-org"`
 
-**Precedence:** If `githubOrganization` is set in the deployment config and `organizations` are also listed in Port mapping, the integration prioritizes single‑organization behavior and syncs only the `githubOrganization`.
+**Precedence:** If `githubOrganization` is set in the environment variables or config and `organizations` are also listed in port mapping, the integration prioritizes single‑organization behavior and syncs only the `githubOrganization`.
 
 **Performance consideration:** Syncing multiple organizations will increase the number of API calls to GitHub and may slow down the integration. The more organizations you sync, the longer the resync time and the higher the API rate limit consumption. Consider syncing only the organizations you need.
 :::
@@ -215,7 +214,7 @@ For example, say you want to manage your `package.json` files in Port. One optio
 The following configuration fetches all `package.json` files from "MyRepo" and "MyOtherRepo", and creates an entity for each of them, based on the `manifest` blueprint:
 
 :::info Organization field in file selectors
-The `organization` field is optional when `githubOrganization` is set in the deployment config. It is required when no deployment-level organization is provided (e.g., Classic PAT with multiple organizations defined in your Port mapping).
+The `organization` field is optional when `githubOrganization` is set in the environment variables and required when it is not provided (e.g., Classic PAT with multiple organizations defined in your port mapping).
 :::
 
 <details>

docs/build-your-software-catalog/sync-data-to-catalog/git/github-ocean/installation/_install_methods.mdx

@@ -131,7 +131,7 @@ To install the integration using ArgoCD:
 :::info Placeholder Replacement Required
 Be sure to replace the `<GITHUB_TOKEN>` and `<GITHUB_ORGANIZATION>` placeholders with your actual values. If you are using a self-hosted GitHub instance, update the `githubHost` value to point to your instance.
 
-For multi-organization support, use a **classic PAT token** and specify multiple organizations in the Port mapping
+For multi-organization support, use a **classic PAT token** and specify multiple organizations in the port mapping
 
 ```yaml showLineNumbers
 deleteDependentEntities: true

docs/build-your-software-catalog/sync-data-to-catalog/git/github-ocean/installation/installation.mdx

@@ -32,8 +32,8 @@ Starting from **version 3.0.0-beta**, the GitHub integration supports syncing da
 
 :::info Multi-organization configuration
 - GitHub App and fine-grained PAT: use `githubOrganization` (single organization).
-- Classic PAT: to sync multiple organizations, list them in your Port mapping under `organizations`.
-- Precedence: if `githubOrganization` is set in the deployment config and `organizations` are listed in Port mapping, the integration syncs only the `githubOrganization` (single‑org behavior).
+- Classic PAT: to sync multiple organizations, list them in your port mapping under `organizations`.
+- Precedence: if `githubOrganization` is set in the environment variables or config and `organizations` are listed in port mapping, the integration syncs only the `githubOrganization` (single‑org behavior).
 - Performance: syncing multiple organizations increases API calls and may slow down the integration.
 :::
 

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

@@ -10,11 +10,10 @@ The new Ocean-powered GitHub integration comes with several key improvements:
 - **Enhanced performance** - Faster resyncs thanks to improved API efficiency, making your data available sooner.
 - **Better selectors** - More granular control over what you sync with improved selectors for `pull requests`, `issues`, `dependabot alerts`, `codescanning alerts`, `files`, and `folders`.
 
-## Major changes
 
-### Multi-organization support (v3.0.0-beta)
+### Multi-organization support
 
-The GitHub integration now supports ingesting data from multiple GitHub organizations starting from **version 3.0.0-beta**. Configure one organization using `githubOrganization`, or list multiple organizations in your Port mapping under `organizations`:
+The GitHub integration supports ingesting data from multiple GitHub organizations starting from **version 3.0.0-beta**. Configure one organization using `githubOrganization`, in your environment variables or list multiple organizations in your port mapping under `organizations`:
 
 ```yaml showLineNumbers
 deleteDependentEntities: true
@@ -26,7 +25,7 @@ organizations:
 # ... rest of your mapping (repositoryType, resources, etc.) ...
 ```
 
-**Precedence:** If `githubOrganization` is set in the deployment config and `organizations` are listed in Port mapping, the integration syncs only the `githubOrganization` (single‑org behavior).
+**Precedence:** If `githubOrganization` is set in the environment variables or config and `organizations` are listed in port mapping, the integration syncs only the `githubOrganization` (single‑org behavior).
 
 ### Authentication model
 
@@ -97,7 +96,7 @@ A key change is how we denote custom attributes. We now add a double underscore
 ### Files & GitOps
 
 ::::info Organization field in file selectors
-The `organization` field is optional when `githubOrganization` is set in the deployment config. It is required when `githubOrganization` is not provided.
+The `organization` field is optional when `githubOrganization` is set in the environment variables and it is required when not provided there.
 ::::
 
 <details>
@@ -402,7 +401,7 @@ resources:
 ### Folders
 
 ::::info Organization field in folder selectors
-The `organization` field is optional when `githubOrganization` is set in the deployment config. It is required when no deployment-level organization is provided (e.g., Classic PAT with multiple organizations defined in your Port mapping).
+The `organization` field is optional when `githubOrganization` is set in the environment variables and is required when not provided (e.g., Classic PAT with multiple organizations defined in your port mapping).
 ::::
 
 For the `folder` kind, the `folder.name` attribute is no longer part of the response. Instead, you can easily derive the folder name from the `folder.path` using a JQ expression, as shown in the example below:
@@ -552,7 +551,7 @@ This section provides a high-level summary of the key changes for mappings.
 
 | Area | Old Value | New Value | Notes |
 |---|---|---|---|
-| **Multi-Organization** | N/A | `githubOrganization` is not optional | **Classic PAT supports multiple orgs using the `organization` parameter in Port mapping; GitHub App and Fine-grained PAT do not support multi organization and there required the `githubOrganization` configuration**. Syncing multiple organizations increases API calls and may slow down the integration. |
+| **Multi-Organization** | N/A | `githubOrganization` is not optional | **Classic PAT supports multiple orgs using the `organization` parameter in port mapping; GitHub App and Fine-grained PAT do not support multi organization and there required the `githubOrganization` configuration**. Syncing multiple organizations increases API calls and may slow down the integration. |
 | **File Organization** | N/A | `organization: "my-org"` | Optional if `githubOrganization` is set; required when not (e.g., Classic PAT multi-org). |
 | **Folder Organization** | N/A | `organization: "my-org"` | Optional if `githubOrganization` is set; required when not set(e.g., Classic PAT multi-org). |
 | **Authentication** | GitHub App Installation | PAT or Self-Created GitHub App | The integration can be authenticated using a Personal Access Token (PAT) or a self-created GitHub App. **Multi-org requires classic PAT**. |