vela-rulesets

Configure conditional step execution in Vela CI/CD pipelines with rulesets.

Updated Mar 7, 2026

Search Tags:#automation #ci/cd #pipeline #conditional execution #rulesets #vela

Ready to run

npx skills add https://github.com/ryanmr/vela-skills --skill vela-rulesets

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vela-rulesets
Source: https://github.com/ryanmr/vela-skills/tree/main/.agents/skills/vela-rulesets
Command: npx skills add https://github.com/ryanmr/vela-skills --skill vela-rulesets

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill allows you to precisely control when specific steps in your CI/CD pipeline execute, preventing unnecessary runs and ensuring actions are taken only under the correct conditions.

Core Features & Use Cases

Conditional Execution: Define rules based on branch, event type, changed files, commit messages, and more.
Compile-time vs. Runtime: Differentiate between rules evaluated before the pipeline starts and those checked during execution.
Use Case: Ensure a deployment step only runs on the main branch during a push event, or trigger a notification only when specific files in the docs/ directory are modified.

Quick Start

Configure a step to run only when a push event occurs on the main branch.

Frequently Asked Questions about vela-rulesets

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I control conditional step execution in Vela CI/CD pipelines?▼

You can control conditional step execution in Vela CI/CD pipelines by using a ruleset engine to define rules based on branch, event type, changed files, and commit messages for granular pipeline control.

What is the difference between compile-time and runtime rules in pipeline automation?▼

Compile-time rules in pipeline automation are evaluated before the pipeline starts, while runtime rules are checked during execution, allowing you to differentiate conditions like branch events from runtime step statuses.

Can I trigger pipeline steps only when specific files are modified?▼

Yes, you can trigger pipeline steps only when specific files are modified by setting path-based conditional execution rules, ensuring actions run exclusively when designated directories like docs/ are changed.

How do I ensure a deployment step only runs on the main branch during a push event?▼

To ensure a deployment step only runs on the main branch during a push event, configure conditional execution rules within your Vela pipeline definition language to match both the branch and event type.

Does this conditional execution ruleset engine require external dependencies?▼

No, this conditional execution ruleset engine requires no external dependencies, integrating directly with Vela's pipeline definition language for declarative configuration of compile-time and runtime conditions.

What are the limitations of using custom expressions for pipeline control?▼

The ruleset engine limits pipeline control to predefined compile-time and runtime conditions including branch, event, path, status, and custom expressions, requiring declarative configuration within Vela's pipeline definition language.