Skill: always wait on a started run with pipelines wait
Agents started runs and moved on, then missed failures. The skill now says to follow every run with a background pipelines wait, read the result when it ends, and act on it instead of polling or promising a report.
This commit is contained in:
@@ -13,7 +13,15 @@ task with the least ceremony, and keep work small enough to verify.
|
||||
|
||||
`pipelines list` shows the registered workflows; `pipelines runs` shows history.
|
||||
Start a run with `pipelines run <name> "<task>"`, and inspect it with
|
||||
`pipelines inspect <id>`. `pipelines wait <id>` blocks until it finishes.
|
||||
`pipelines inspect <id>`.
|
||||
|
||||
After starting a run, always follow it with `pipelines wait <id>` until it
|
||||
finishes; never start a run and move on without waiting. Run the wait as a
|
||||
background command (one per run, or one loop over several ids) so the session is
|
||||
notified the moment the run ends, then read its result with
|
||||
`pipelines inspect <id> --json` and act on it: land, retry, or fix and report.
|
||||
Do not poll with repeated `pipelines runs` calls, and do not tell the user a run
|
||||
is done, or will be reported, without a wait covering it.
|
||||
|
||||
A failed run keeps its worktree and commits. Read `pipelines inspect <id> --json`
|
||||
before deciding: resume the failed stage (`pipelines retry <id>`), fix directly,
|
||||
|
||||
Reference in New Issue
Block a user