stado change submit
Invocation
stado change submit [OPTIONS] --commit <COMMIT> <CHECKOUT>Purpose
Queue a commit to land on its repository's main: the commit is written again on the remote main, checked with the product's declared gates, reviewed as its risk requires and pushed by `stado change run`. A commit that changes more lines than its product's catalog `submit.max_changed_lines` is refused here, to be split, and so is a high-risk one that names no `--defect`
Required inputs and options
| Input or option | Contract |
|---|---|
<CHECKOUT> | The repository's checkout on this machine |
--commit <COMMIT> | The commit to land: one the checkout holds, or one origin gives by its id |
--defect <DEFECTS> | An Oko defect the commit repairs; repeat for several. The first scopes the harsh review, so a high-risk change must name one; each is recorded repaired when the change lands |
--json | Command option; required or optional as shown in the invocation. |
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
- The first scopes the harsh review, so a high-risk change must name one; each is recorded repaired when the change lands
- 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.