Skip to content

Commit d4cff2e

Browse files
authored
Merge pull request #650 from linear-b/add-limitation-info
added info on limits
2 parents d573314 + 1b4e344 commit d4cff2e

File tree

5 files changed

+51
-0
lines changed

5 files changed

+51
-0
lines changed

docs/execution-model.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,18 @@ gitStream is triggered on new pull requests (PRs) for repositories that have git
66

77
When a central `cm` repository is set with the CI/CD runner, the events for PRs from all installed repositories shall be evaluated in the `cm` repository pipeline, considering the organization-level and PR repository rules.
88

9+
## Execution behavior for free accounts
10+
11+
Free accounts have a monthly limit on the number of PRs that can trigger automations. Once this limit is reached:
12+
13+
- PRs will still be created, but gitStream will skip automations for them.
14+
- The gitStream check on these PRs will be concluded as `Skipped`, to ensure that gitStream will not block the PR from merging.
15+
- A warning is displayed in PR comments when the organization reaches 90% of its quota.
16+
- The limit resets at the start of each month.
17+
18+
To remove automation limits, <a href="https://linearb.io/contact-us" target="_blank">Contact LinearB</a> and upgrade to a paid plan.
19+
🔗 Learn more: [Automation Limits](limits.md)
20+
921
## Triggering Mechanism
1022

1123
gitStream automations are triggered by events related to pull requests (PRs). You can specify triggers to fine-tune which events should initiate automations.

docs/faq.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,17 @@ To support automations that either Approve or Merge PRs, the git providers requi
2525

2626
gitStream supports repositories in GitHub, GitLab, and Bitbucket. Note that the `add-label` action is not supported in Bitbucket as it does not have a native labeling feature.
2727

28+
## Are there limits on gitStream automations for free accounts?
29+
30+
Yes. Free accounts have a monthly limit on the number of PRs that can trigger automations.
31+
32+
- When the organization reaches 90% of the limit, a warning will appear in PR comments.
33+
- Once the limit is exceeded, new PRs will not trigger automations and will be marked as "Skipped."
34+
- The limit resets at the start of each month.
35+
36+
To remove automation limits, <a href="https://linearb.io/contact-us" target="_blank">Contact LinearB</a> and upgrade to a paid plan.
37+
🔗 Learn more: [Automation Limits](limits.md)
38+
2839
## Can I use gitStream with Merge Queues?
2940

3041
Yes. When a merge queue is used, and gitStream is set as a required check, gitStream automation will be invoked with the merge event. The automation will set gitStream to a `Completed` status and `Skipped` conclusion to allow the PR merge.

docs/index.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -75,6 +75,14 @@ gitStream is a workflow automation tool that enables you to use YAML configurati
7575

7676
That's it! Now sit back and watch gitStream run automation rules on your next PR.
7777

78+
!!! warning "Automation limits for free accounts"
79+
Free accounts have a monthly cap on PRs that can trigger gitStream automations.
80+
81+
- At 90% usage, a warning appears in PR comments.
82+
- Once the limit is reached, new PRs will not run automations and the gitStream check will be concluded as `Skipped`.
83+
- Limits reset at the start of each month.
84+
85+
🔗 Learn more: [Automation Limits](limits.md)
7886

7987
## Get Involved
8088
Want to report a bug, request a new feature, ask a question, get updates for new features, or propose a new configuration for the automation library? [Join us on GitHub](https://github.com/linear-b/gitstream).

docs/limits.md

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
# Automation limits for free accounts
2+
3+
## Monthly PR automation limit
4+
5+
Free accounts have a monthly cap on the number of PRs that can trigger automations in their organization. This limit ensures fair usage while allowing teams to experience gitStream’s benefits before upgrading.
6+
7+
### How it works
8+
- When the account reaches 90% of its quota, a warning appears in PR comments.
9+
- Once the limit is reached, new PRs will not execute automations and the gitStream check will be concluded as `Skipped`.
10+
- The limit resets at the start of each month.
11+
12+
### What happens when the limit is reached?
13+
- PRs that exceed the quota will still be created as usual, but gitStream will not process automations on them.
14+
- The PR check will indicate that automations were skipped due to limits.
15+
16+
## Need more automations?
17+
If your team requires a higher automation quota, upgrading to a paid plan will remove these restrictions.
18+
19+
<a href="https://linearb.io/contact-us" target="_blank">Contact LinearB</a> or <a href="https://linearb.io/book-a-demo" target="_blank">Book a demo</a> to explore upgrade options.

mkdocs.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,7 @@ nav:
2222
- Reference:
2323
- Configuration: cm-file.md
2424
- Execution: execution-model.md
25+
- Automation Limits: limits.md
2526
- Context variables: context-variables.md
2627
- Filter functions: filter-functions.md
2728
- Automation actions: automation-actions.md

0 commit comments

Comments
 (0)