gitStream is triggered on new pull requests (PRs) for repositories that have gitStream installed. Upon triggering, gitStream collects context variables and evaluates the automation rules to determine which automation rules are relevant.
Organization level rules and repository rules
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, taking into account the organization level rules and the PR repository rules.
By default, gitStream evaluates any new commit that is pushed to the PR, triggering automation evaluation.
Additionally, if any of the automation rules reference the
pr context, gitStream shall trigger and will initiate automation rules evaluation even where there are changes to the PR title, descriptions, labels or comments.
This allows for greater flexibility in the automation process, ensuring that the relevant automation rules are evaluated and triggered when necessary. The execution model ensures that the automation process is streamlined, efficient, and effective.
gitstream supports an explicit triggering mechanism. When using explicit triggers, the automations will run only according to the defined triggers, which means the Implicit triggers will not work. Automations triggered by explicit triggers will also be invoked on
Explicit triggers syntax
Use explicit triggers to enhance the control and customization of automations in gitStream, allowing users to define precisely when and how automations should be triggered based on various events and actions within pull requests.
on keyword to the file and/or to a specific automation to define explicit triggers. gitStream supports the following explicit triggers:
| ||Trigger when merging the PR|
| ||Trigger when the PR is created|
| ||Trigger on each commit after the creation of the PR|
| ||Trigger on each added comment|
| ||Trigger on each added label|
| ||Trigger on removed label|
Explicit triggers are set per each automation block independently and can be configured at the file level, specific to each automation separately or a combination of the two. In case triggers are listed at the file level and specific automation, the automation will be triggered according to both triggers. If an automation block does not have explicit triggers configured, it will be triggered according to the default (implicit) triggers
assign code expert reviewer when the PR is created and after each commit
Explain code experts only if the label “suggest-reviewer” exists. The automation will be triggered after each commit and after each label addition. If the label “suggest-reviewer” exists, it will trigger the