Configure Webhook Events

Control when pipelines trigger based on branch-specific activities in your repositories.

If a pipeline is running and a new commit arrives on a matching branch, it queues one additional run for the latest commit only.

Repository and Branch Step

1. Login → Pipelines → open pipeline → click Workflow.

2. Click the settings icon in the Start of Workflow box → fill in Repository fields.

3. Switch to the Webhooks tab to configure trigger options.

Field	Details
Platform	GitHub, GitLab, GitHub Mono Repo, Azure DevOps, Bitbucket
Primary / Secondary Branch	Individual branches to monitor
Branch Pattern	Wildcards e.g. release/*, feature/**

Trigger Options

Option	Behavior
Push Events	Triggers when code is pushed to the repo
Pull Request Events	Triggers on any PR action
PR Created / Approved	Triggers on PR open or reviewer approval
Dynamic Branch Switching	Webhook runs can target branches other than the main branch
Secrets	Encrypts a token; only matching webhook requests are processed

💡 Copy theWebhook URLand add it to your SCM's webhook settings.

PR Status Update

• A comment is auto-added to the PR showing Pipeline ID, run count, and result.

• Detailed step updates include run count, status, and logs.

• Multiple pipelines can be associated with a single PR.

• All checks must pass before merging — blocking unvalidated code.