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
If you're working with a large repository (typically monorepos) and experience timeout issues during GitHub Actions execution, you can use the lite version of gitStream that performs a shallow clone to reduce execution time:
72
+
73
+
```yaml
74
+
jobs:
75
+
gitStream:
76
+
timeout-minutes: 15
77
+
runs-on: ubuntu-latest
78
+
name: gitStream workflow automation
79
+
steps:
80
+
- name: Evaluate Rules
81
+
uses: linear-b/gitstream-github-action@v2-lite
82
+
id: rules-engine
83
+
```
84
+
85
+
**Important:** The lite version has limitations - automations that rely on Git history (such as code-experts) may not work properly due to the shallow clone.
86
+
61
87
!!! Success
62
88
When finished, you should have the following file structure in your repo.
63
89
@@ -96,6 +122,32 @@ You can set up gitStream for a single repo or your entire GitHub organization. S
If you're working with large repositories in your organization (typically monorepos) and experience timeout issues during GitHub Actions execution, you can use the lite version of gitStream that performs a shallow clone to reduce execution time:
136
+
137
+
```yaml
138
+
jobs:
139
+
gitStream:
140
+
timeout-minutes: 15
141
+
runs-on: ubuntu-latest
142
+
name: gitStream workflow automation
143
+
steps:
144
+
- name: Evaluate Rules
145
+
uses: linear-b/gitstream-github-action@v2-lite
146
+
id: rules-engine
147
+
```
148
+
149
+
**Important:** The lite version has limitations - automations that rely on Git history (such as code-experts) may not work properly due to the shallow clone. See the [troubleshooting section](/troubleshooting/#github-timeout-issues-with-large-repositories) for more details.
150
+
99
151
!!! Success
100
152
Once finished, **all** PRs to your organization's repositories will be processed by the GitHub Action in this repo, and your `cm` repo should have a file directory that looks like this.
@@ -129,7 +129,7 @@ Clicking the `Details` button will show more information and context.
129
129
130
130
You can add this automation to see details on context variable.
131
131
132
-
####gitStream fails when using template strings with special characters (e.g., colon ':')
132
+
## gitStream fails when using template strings with special characters (e.g., colon ':')
133
133
134
134
If a template string (e.g., pull request title, description, or other context variables) contains special characters such as a colon (`:`), gitStream might fail with a YAML parsing error due to invalid syntax.
135
135
@@ -140,6 +140,35 @@ comment: |
140
140
{{ pr.title }}
141
141
```
142
142
143
+
## GitHub timeout issues with large repositories
144
+
145
+
If you're experiencing timeout issues during GitHub Actions execution, particularly with large repositories or monorepos, this is typically caused by the time required to clone the entire repository history.
146
+
147
+
You can resolve this by using the **lite version** of the gitStream GitHub Action, which performs a shallow clone to reduce execution time:
148
+
149
+
```yaml
150
+
jobs:
151
+
gitStream:
152
+
timeout-minutes: 15
153
+
runs-on: ubuntu-latest
154
+
name: gitStream workflow automation
155
+
steps:
156
+
- name: Evaluate Rules
157
+
uses: linear-b/gitstream-github-action@v2-lite
158
+
id: rules-engine
159
+
```
160
+
161
+
**Important limitations of the lite version:**
162
+
- Automations that rely on Git history (such as `code-experts`) may not work properly due to the shallow clone
163
+
- Historical data analysis features will be limited
164
+
- Some context variables that depend on full Git history may return incomplete results
0 commit comments