From eaf0c4046d9d6d18d4296915ff39efe06f50552c Mon Sep 17 00:00:00 2001 From: Ofer Affias Date: Thu, 22 May 2025 18:28:14 +0300 Subject: [PATCH] fix the bullet list not showing up correctly --- docs/bitbucket-installation.md | 2 +- docs/github-installation.md | 2 +- docs/gitlab-installation.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/bitbucket-installation.md b/docs/bitbucket-installation.md index f7290e450..b55829ab1 100644 --- a/docs/bitbucket-installation.md +++ b/docs/bitbucket-installation.md @@ -26,7 +26,6 @@ description: Install gitStream to your Bitbucket workspace. 1. **Webhook Event Handling by gitStream** When Bitbucket triggers a webhook event (e.g., a pull request opened), gitStream may need to make follow-up API calls to Bitbucket. This can include fetching additional metadata, posting comments to the PR, or performing other actions. These calls are made from the LinearB/gitStream service, which uses a fixed set of IP addresses. These IPs must be added to your Bitbucket allowlist to ensure proper operation. - 2. **Outbound Requests from Your CI Runner** When your pipeline runs gitStream, that runner might also make outbound calls to Bitbucket—for example, to clone a repository or retrieve commit history. These requests will originate from the runner's IP address. @@ -34,6 +33,7 @@ description: Install gitStream to your Bitbucket workspace. **Recommended Solution** To ensure reliability: + - Add LinearB/gitStream service IPs to your Bitbucket allowlist (listed above). - Use self-hosted runners or runners with static IPs so you can manage and allowlist their addresses explicitly. diff --git a/docs/github-installation.md b/docs/github-installation.md index 6744c8025..715d4c049 100644 --- a/docs/github-installation.md +++ b/docs/github-installation.md @@ -17,7 +17,6 @@ description: Install gitStream to your GitHub organization. 1. **Webhook Event Handling by gitStream** When GitHub triggers a webhook event (e.g., a pull request opened), gitStream may need to make follow-up API calls to GitHub. This can include fetching additional metadata, posting comments to the PR, or performing other actions. These calls are made from the LinearB/gitStream service, which uses a fixed set of IP addresses. These IPs must be added to your GitHub allowlist to ensure proper operation. - 2. **Outbound Requests from Your CI Runner** When your pipeline runs gitStream (e.g., via a GitHub Action), that runner might also make outbound calls to GitHub—for example, to clone a repository or retrieve commit history. These requests will originate from the runner's IP address. @@ -25,6 +24,7 @@ description: Install gitStream to your GitHub organization. **Recommended Solution** To ensure reliability: + - Add LinearB/gitStream service IPs to your GitHub allowlist (listed above). - Use self-hosted runners or runners with static IPs so you can manage and allowlist their addresses explicitly. diff --git a/docs/gitlab-installation.md b/docs/gitlab-installation.md index 93711bd61..142e1db6d 100644 --- a/docs/gitlab-installation.md +++ b/docs/gitlab-installation.md @@ -20,7 +20,6 @@ description: Install gitStream to your GitLab organization. 1. **Webhook Event Handling by gitStream** When GitLab triggers a webhook event (e.g., a merge request opened), gitStream may need to make follow-up API calls to GitLab. This can include fetching additional metadata, posting comments to the MR, or performing other actions. These calls are made from the LinearB/gitStream service, which uses a fixed set of IP addresses. These IPs must be added to your GitLab allowlist to ensure proper operation. - 2. **Outbound Requests from Your CI Runner** When your pipeline runs gitStream, that runner might also make outbound calls to GitLab—for example, to clone a repository or retrieve commit history. These requests will originate from the runner's IP address. @@ -28,6 +27,7 @@ description: Install gitStream to your GitLab organization. **Recommended Solution** To ensure reliability: + - Add LinearB/gitStream service IPs to your GitLab allowlist (listed above). - Use self-hosted runners or runners with static IPs so you can manage and allowlist their addresses explicitly.