Steps

The scripts a workflow actually runs, in order.

Contents

A step has a name, a script, and an optional working folder. The script is edited in a code editor with syntax highlighting for the workflow's shell, and can be as many lines as you need.

Steps run in order — on this computer with the workflow's shell (see Run on this computer), or over SSH on the workflow's server.
Each step starts in the project's local folder (on this computer) or the server's remote deploy path (on a server). Set a step's working folder to start somewhere else; a relative path like ..\builder is resolved from there.
All of the project's environment variables and secrets are available to every step.
If a step fails, the run stops and every step after it is marked skipped — later steps never run.
Drag a step by its handle to reorder it, or use the copy button to duplicate it.

A complete step list for building a Node app might be:

Step	Script
Install	`npm ci`
Test	`npm test`
Build	`npm run build`

You could also put all three commands in one step, one per line. Splitting them out gives you a status, a duration and a log per step in the run panel.

Working folders, the shell and artifact paths are saved on the computer where you set them (like the local folder), so a second computer running CID starts with the defaults.

Run on this computer Manual trigger

$ loading▍

Steps

Ask Pumpkin

Hi, I'm Pumpkin.

Steps