Triggers
A trigger defines when a pipeline runs. Each pipeline has exactly one trigger, configured at the pipeline level (not on any individual step).
Setting a trigger
Open your pipeline in the editor. Click the Trigger button in the top toolbar.
A panel opens where you select the trigger type and its parameters.
INFO
A trigger is required before you can set a pipeline to Active status. Draft pipelines can be saved and exported without one.
Trigger types
Push
Fires when code is pushed to one or more branches.
| Parameter | Description | Example |
|---|---|---|
| Branches | List of branch name patterns | main, release/* |
Patterns support glob syntax: feature/* matches any branch starting with feature/.
Typical use: CI pipeline that runs on every commit to main and all release/ branches.
# Generated GitHub Actions output
on:
push:
branches:
- main
- release/*Pull Request
Fires when a pull request is opened, synchronized, or reopened against specified branches.
| Parameter | Description | Example |
|---|---|---|
| Target branches | Branches the PR targets | main, develop |
Typical use: Run tests and lint checks on every PR before merge.
Schedule
Fires automatically on a cron schedule.
| Parameter | Description | Example |
|---|---|---|
| Cron expression | Standard 5-field cron | 0 2 * * * |
Cron reference:
┌───── minute (0-59)
│ ┌───── hour (0-23)
│ │ ┌───── day of month (1-31)
│ │ │ ┌───── month (1-12)
│ │ │ │ ┌───── day of week (0-7, 0 and 7 are Sunday)
│ │ │ │ │
* * * * *Common schedules:
| Expression | Meaning |
|---|---|
0 2 * * * | Every day at 2:00 AM |
0 9 * * 1 | Every Monday at 9:00 AM |
0 */6 * * * | Every 6 hours |
0 0 1 * * | First day of every month |
Typical use: Nightly build, weekly dependency update check, scheduled database backup.
Tag
Fires when a Git tag is pushed matching a pattern.
| Parameter | Description | Example |
|---|---|---|
| Tag patterns | Tag name patterns | v*, release-* |
Typical use: Release pipeline triggered by pushing a version tag like v1.2.3.
Manual
The pipeline does not run automatically. It must be triggered manually via the CI platform's UI or API.
No additional parameters.
Typical use: Production deployments that require a human decision before running.
Updating a trigger
You can change a pipeline's trigger at any time. Open the Trigger panel, make your changes, and click Save. The next YAML export will reflect the new trigger.