You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#### Using org level? Did you enable gitStream for your `cm` repo
44
54
45
55
Make sure you have added the `cm` repo to the repos gitStream should run on
46
56

47
57
#### Are you using the default runners along with the "IP allow list" feature on GitHub?
48
-
<ahref="https://docs.github.com/en/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list"target="_blank">According to GitHub</a>, in order to use GitHub actions with the allow list, you must use self-hosted runners or GitHub-hosted larger runners with static IP address ranges and add their IP to the allow list.
58
+
<ahref="https://docs.github.com/en/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list"target="_blank">According to GitHub</a>, in order to use GitHub actions with the allow list, you must use self-hosted runners or GitHub-hosted larger runners with static IP address ranges and add their IP to the allow list.
49
59
50
60
When using GitHub's default runners, you will encounter the following error: "The repository owner has an IP allow list enabled, and [IP] is not permitted to access this repository," which indicates that GitHub is blocking the action. You can verify if the IP is part of GitHub's CIDR ranges by using the following <ahref="https://api.github.com/meta"target="_blank">list</a>
51
61
@@ -59,8 +69,8 @@ This error indicates that gitStream is unable to locate the file `.github/workfl
59
69
60
70
## I have rules that should have blocked merge, but the PR can be merged still
61
71
62
-
For example, when using the [`set-required-approvals`](/automation-actions#set-required-approvals)
63
-
action, gitStream can ensure the PR got enough approvals before it can be merged. gitStream does that
72
+
For example, when using the [`set-required-approvals`](/automation-actions#set-required-approvals)
73
+
action, gitStream can ensure the PR got enough approvals before it can be merged. gitStream does that
64
74
by running as a check and marking the check conclusion as failed. In order for the PR to be blocked, gitStream should be set as a required check in the repo: [instructions here](/github-installation#github-merge-block).
@@ -69,7 +79,7 @@ by running as a check and marking the check conclusion as failed. In order for t
69
79
70
80
In order for gitStream to be listed as a required check, it needs to be triggered at least once in that repo. First create a new PR so gitStream is triggered.
@@ -79,7 +89,7 @@ Check it under repository's Settings > Branches:
79
89
80
90
When using repository level rules, you can edit the `.github/workflows/gitstream.yml` and uncomment the `if` line, you can edit and replace the bot name with the bot name you want to ignore (`dependabot[bot]` in the example below).
0 commit comments