CLI reference / builds / edit

stado builds edit

Invocation

stado builds edit [OPTIONS] <NAME>

Purpose

Change a recipe's source or build definition in place. Every flag is optional and a flag not given leaves its field alone; `--artifact` and `--platform`, when given at all, REPLACE the recorded list. `enabled` is not editable here: `enable` and `disable` own it

Required inputs and options

Input or optionContract
<NAME>Positional input; required or optional as shown in the invocation.
--repo <REPO>HTTPS clone URL of the repository to build. Changing it clears the last seen ref and the recorded runs
--branch <BRANCH>Branch the poller watches. Changing it clears the last seen ref and the recorded runs
--command <COMMAND>Single POSIX sh build command run in the checkout
--artifact <ARTIFACTS>Path in the checkout to upload as a build artifact (repeatable); the paths given replace the recorded ones
--platform <PLATFORMS>Release platform to build for (repeatable); the platforms given replace the recorded ones. A newly named platform simply has no run yet
--auto-declareDeclare a successful run's tag version on every registry host of that platform. Never promotes a signed release
--no-auto-declareStop declaring versions from successful runs
--interval-seconds <INTERVAL_SECONDS>Poll cadence in seconds
--jsonEmit the updated recipe as JSON

Output and state effect

It performs the operation described above and emits its operator result on standard output or standard error. Any state change is limited to the resources and records named by the purpose and options on this page.

Refusals

  • Before dispatch, Stado refuses a missing required token shown in the invocation, an unknown option, or a value outside a listed value set; argument-usage failures exit with code 2.