Skip to Content
kusaw docsv1.0.0

What success looks like

A finished first run leaves a local commit on the factory branch and a `SUMMARY.md`. Kusaw never pushes or merges; merging is yours.

A finished first run leaves a local commit on the factory branch and a SUMMARY.md. Kusaw never pushes or merges; merging is yours.

Run states

A successful run moves through these states, in order:

  • queued — the task is on the factory queue.
  • running — a worker has the run and is executing pipeline steps.
  • waiting_for_human — a gate is waiting for approve or reject. The default pipeline has no gate, so a first run may skip this state.
  • succeeded — the pipeline finished and the local commit is in your repo.

Other endings:

  • failed — a pipeline step did not pass. See Guides and Troubleshooting.
  • needs_attention — the run stopped in a state a person has to look at, for example a loop that gave up. See Guides and Troubleshooting.
  • stopped — a person or the watchdog halted the run. See Guides and Troubleshooting.

Where the result is

The delivered commit is on the factory branch in your repo, not on main. Look at it with git log and git show. SUMMARY.md is the delivery note for that run.

The factory never pushes or merges. You merge when you are ready.

Logs and artifacts

Logs and artifacts are on the run page in the Dashboard and in kusaw runs show.

Next steps

  • Concepts — factories, repos, and the registry.
  • Writing a good task — in Guides.
  • Custom steps — adding your own pipeline steps.

On this page