Configure conditional step execution in Vela CI/CD pipelines with rulesets.
npx skills add https://github.com/ryanmr/vela-skills --skill vela-rulesets
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
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.
main branch during a push event, or trigger a notification only when specific files in the docs/ directory are modified.Configure a step to run only when a push event occurs on the main branch.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
ryanmrCreate .vela.yml pipeline configuration files for the Vela CI/CD system.
lirrensiSend desktop notifications from the terminal via Toast, osascript, or notify-send.
ryanmrExplain Vela CI/CD environment variable scoping and substitution syntax.
JNZader-VaultConfigure Woodpecker CI pipelines for Docker builds and deployments on Gitea/Forgejo.