Vibeham Docs

Workflows let you automate what happens when code is pushed, a pull request is opened, or a deployment completes. Each service comes with pre-configured workflows that you can customize.

Accessing Workflows

Navigate to your project
Click on a service
Select the Workflows tab

How Workflows Work

A workflow has two parts:

Trigger — the event that starts it (push, pull request, deployment, build, or manual)
Steps — the actions to perform (build, deploy, review, scan, etc.)

When the trigger fires, the steps run automatically. Steps at the same position run in parallel; steps at a higher position wait for the previous ones to finish.

Default Workflows

When you first open the Workflows tab, default workflows are created for your service:

Workflow	Trigger	What It Does
Deploy on Push	Push to branch	Builds, deploys, and runs service analysis in parallel
Manual Deploy	Deploy button	Builds and deploys on demand (always available)
Preview Deployments	Pull request	Creates a preview environment for each PR
AI Code Review	Pull request	Runs AI code review and posts a PR comment
Changelog	PR closed	Auto-generates changelog entries from merged PRs
AI Project Scan	Build success	Runs a full AI project scan after successful stable builds

Deploy on Push, Manual Deploy, and Preview Deployments are enabled by default when a service is created. AI-powered workflows (AI Code Review, Changelog, AI Project Scan) start disabled and require AI features to be enabled at the organization level.

Adding a Workflow

Click Add Workflow in the top right
Choose a template from the gallery
Configure the workflow name, trigger settings, and notifications
Click Create

Some templates (like Deploy on Push) are singletons — only one instance is allowed per service. These show "Added" in the gallery if already present.

Configuring Triggers

Each trigger type has its own settings:

Push

Branch — which branch triggers the workflow. Leave empty for the service's default branch. Supports glob patterns (e.g. feat/*, release/*).

Pull Request

Source Branch Pattern — glob pattern for the PR's source branch (e.g. * for all, feat/* for feature branches). The Preview Deployments workflow defaults to feat/*.
Target Branch — optionally override which branch the PR must target (defaults to service's default branch)
PR Actions — which PR events trigger the workflow:
- Opened — when a PR is first created
- Synchronize — when new commits are pushed to the PR
- Closed / Merged — when the PR is closed or merged

Deployment Success / Failed

Environment Type — filter by Stable or Preview (leave empty to match any)

Build Success / Failed

Environment Type — filter by Stable or Preview (leave empty to match any)

Manual

No configuration needed. Triggered from the deploy button in the UI.

Editing a Workflow

Click the pencil icon on any workflow card
Update the name, description, trigger settings, or notifications toggle
Click Save

Enabling / Disabling

Toggle the switch on any workflow card to enable or disable it. Disabled workflows won't run but keep their configuration.

Deleting a Workflow

Click the trash icon on the workflow card
Confirm deletion

Deleted workflows can be re-added from the template gallery.

Notifications

Each workflow has a Notifications toggle. When enabled, the workflow sends notifications through your project's configured notification channels (Slack, webhooks).

Understanding the Workflow Card

Each workflow card shows:

Name and trigger badge (Push, Pull Request, etc.)
Branch configuration — e.g. feat/* → main for PR workflows, branch: main for push
Steps — the sequence of actions (e.g. "Build & Deploy → Service Analysis")
Enable/disable toggle

Workflows