trigggers-refinement #604
trigggers-refinement #604
Conversation
PavelLinearB
commented
Oct 29, 2024
PavelLinearB
commented
![orca-security-us[bot]](https://avatars.githubusercontent.com/in/276250?s=60&v=4){kind=small}
There was a problem hiding this comment.
Orca Security Scan Summary
| Status | Check | Issues by priority | |
|---|---|---|---|
 Passed |
Infrastructure as Code |  0  0  0  0 |
View in Orca |
| Passed |
Secrets | 0 0 0 0 |
View in Orca |
| Passed |
Vulnerabilities | 0 0 0 0 |
View in Orca |
|
| The `triggers` section in gitStream gives you precise control over when automations execute. It allows you to define conditions based on pull request events using `include` and `exclude` lists to specify branch and repository patterns. These lists determine which branches or repositories trigger or bypass automation but do not affect the events initiating automations. | ||
|
|
||
| The `triggers` is section specifies when automations are executed, supporting `include` and `exclude` lists for branch and repository patterns at the file level. | ||
|
|
||
| The `on` keyword can also be used within individual automations to define specific events that trigger those automations. Add the `on` keyword under the `triggers` key in the file and/or to a specific automation to define explicit triggers. | ||
| Additionally, the `on` keyword defines specific events that trigger automations. It can be added at the file level (under the `triggers` section) or within individual automations for greater customization. Multiple triggers can be stacked, meaning gitStream will execute the automation for each matching triggering event, allowing flexibility in defining automation behavior |
There was a problem hiding this comment.
The triggers section in gitStream controls when automations run. Use include and exclude lists to specify branch and repository patterns that trigger or bypass automation, without affecting event initiation.
The on keyword defines specific triggering events and can be used at the file level (in triggers) or within individual automations. Triggers are combined using an AND relation, meaning all conditions must match for the automations to execute.
Example: Run automation on pr_created and if the branch name includes the word "fix_".
There was a problem hiding this comment.
"Triggers are combined using an AND relation, meaning all conditions must match for the automations to execute." Is not true. These are triggering events, and one of them is enough to trigger gitStream
That's why I want to avoid the use of OR/AND. It is confusing, and an explanation seems enough IMO.
Examples are available at the bottom of the file
