Skip to content

Conversation

emekanwaoma
Copy link
Contributor

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.

Added docs pages

Please also include the path for the added docs

  • Quickstart (/)
  • Blueprint (/platform-overview/port-components/blueprint)
  • ...

Updated docs pages

Please also include the path for the updated docs

  • Quickstart (/)
  • Blueprint (/platform-overview/port-components/blueprint)
  • ...

Copy link

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-2885.d2ngvl90zqbob8.amplifyapp.com

Comment on lines 37 to 38
- **With classic PAT**: Specify a list of organizations: `githubOrganizations: ["org1", "org2", "org3"]`
- **With classic PAT**: Leave empty to sync all organizations the PAT user is a member of: `githubOrganizations: []`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

DRY

Copy link
Collaborator

@kodjomiles kodjomiles left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please update the description with the link to the document in preview mode following the description template

Comment on lines 33 to 55
:::warning Breaking change in v2.0.0-beta
The configuration parameter has changed from `githubOrganization` (singular) to `githubOrganizations` (plural, array format). You must update your configuration when upgrading to v2.0.0-beta.

**Before:**
```yaml
githubOrganization: "my-org"
```
**After (v2.0.0-beta):**
```yaml
githubOrganizations: ["my-org"] # Now an array
```
:::
:::info Authentication requirements
- **Classic PAT**: Supports multiple organizations
- **Fine-grained PAT**: Does NOT support multi-organization
- **GitHub App**: Supports exactly **one organization** only
:::
:::caution Performance impact
Syncing multiple organizations increases API calls and may slow down the integration. Consider syncing only the organizations you need.
:::
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't use two or more admonitions in a row

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Find another way to communicate this

Comment on lines 27 to 34
:::info Authentication requirements
- **Classic PAT**: Supports multiple organizations. Fine-grained PAT tokens do not support multi-organization authentication.
- **GitHub App**: Only supports a **single organization** (minimum 1, maximum 1). You must specify exactly one organization in the `githubOrganizations` array.
:::

:::caution Performance impact
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.
:::
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comment about the admonition

Comment on lines 25 to 32
:::warning Authentication limitations
- **Classic PAT**: Supports multiple organizations. Fine-grained PAT tokens do not support multi-organization authentication.
- **GitHub App**: Only supports a **single organization** (minimum 1, maximum 1). You must specify exactly one organization in the `githubOrganizations` array.
:::

:::caution Performance impact
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.
:::
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants