Configure full Docker setup and confirm consequential actions
This commit is contained in:
+16
-5
@@ -157,7 +157,7 @@ you invoked Pipelines from), alongside the task and any custom input fields.
|
||||
It is recorded by the server and shown in the run's Input section.
|
||||
|
||||
Press `r` or use `:retry` on a failed run to restart it from the first stage.
|
||||
CLI equivalent: `pipelines retry <run-id>` (optional `--json`, `--wait`, and
|
||||
CLI equivalent: `pipelines retry <run-id>` (optional `--yes`, `--json`, `--wait`, and
|
||||
`--request-key`). The new attempt retains the initial input, directory, pinned
|
||||
pipeline version, and edit scope, and records `retry_of`. Original history is
|
||||
unchanged. Legacy runs gain `pwd` from their recorded workspace on retry.
|
||||
@@ -212,7 +212,8 @@ published definition. Submission remains separate and explicit.
|
||||
In the draft browser, `x` asks to delete the selected draft; `y` confirms and
|
||||
Esc or `n` keeps it. The CLI equivalent, `pipelines draft-delete <draft.md>`, is
|
||||
an explicit deletion command and needs no server connection; `--json` reports
|
||||
the result. Only managed drafts inside the configured draft cache are accepted.
|
||||
the result. It asks for confirmation; `--yes` explicitly approves scripted deletion.
|
||||
Only managed drafts inside the configured draft cache are accepted.
|
||||
Source and metadata symlinks/directories and external Markdown files are
|
||||
rejected. Published definitions and run history are not deleted. Cleanup can
|
||||
also remove orphaned metadata when a draft source was already removed.
|
||||
@@ -230,14 +231,24 @@ an immutable version in JSON mode. Starting a run enables its stage-declared too
|
||||
without a second approval. Editing supports all file types and new files within
|
||||
the run directory; no file list is required. Shell commands use the repository's
|
||||
actual tooling. `--write-paths` is an optional narrower scope, not a prerequisite.
|
||||
`--yes` and `--allow-tools` remain compatibility flags but are not required.
|
||||
`--yes` skips action confirmation for explicitly approved automation;
|
||||
`--allow-tools` remains a compatibility flag and is not required.
|
||||
`--wait` polls until terminal status, returns nonzero on failure/cancellation,
|
||||
and does not cancel a run when waiting times out. Reuse `--request-key` to prevent
|
||||
duplicate work. A supplied pipeline/task starts immediately with a live inspector.
|
||||
When a task is omitted, Enter inserts a newline and Ctrl+S runs the composed task.
|
||||
duplicate work. A supplied pipeline/task opens an action-confirmation popup before
|
||||
starting with a live inspector (unless `--yes` was supplied). When a task is omitted,
|
||||
Enter inserts a newline and Ctrl+S opens the confirmation for the composed task.
|
||||
There is no file-list question or typed RUN confirmation. Shell runs with your
|
||||
user's authority: the run directory and tool policy are not an OS sandbox.
|
||||
|
||||
Run, retry, cancellation, CLI publication, and draft deletion require confirmation.
|
||||
CLI prompts go to stderr and default to No; use `--yes` for non-interactive approval.
|
||||
The TUI's run/retry/cancel popup accepts `y`; Enter does not implicitly approve,
|
||||
and `n`/Esc cancels without sending the action. Retry restarts with new sessions
|
||||
and original input/pwd, never the failed conversation; side effects may repeat.
|
||||
Publication retains its explicit submission confirmation and version conflict guards.
|
||||
Quit with `:quit`, not `q`; Ctrl+C remains an interrupt.
|
||||
|
||||
JSON results go to stdout, errors to stderr (JSON error envelopes when requested),
|
||||
and failures exit nonzero. Export/template `--source` deliberately prints raw
|
||||
Markdown. `--timeout` bounds each server request and the optional wait duration.
|
||||
|
||||
Reference in New Issue
Block a user