Allow portable drafts to publish to the connected server
This commit is contained in:
+8
-2
@@ -84,8 +84,14 @@ publishes it. CLI `pipelines new` retains its existing direct-OpenCode behavior;
|
||||
Press `d` on the dashboard or use `:drafts` to browse the same retained drafts as
|
||||
`pipelines drafts`. Use `n/p` to select, `j/k` to scroll source, `e`/Enter to reopen
|
||||
the existing draft, `v` for server validation, and `s` for submission confirmation.
|
||||
`r` refreshes the list. Submission preserves create-only/version guards and rejects
|
||||
drafts belonging to another server. For unnamed drafts, submission asks you to
|
||||
`r` refreshes the list. Drafts can be validated, edited, and submitted to whichever
|
||||
server you are connected to. Same-server submissions preserve create-only/version
|
||||
guards. A different destination imports the draft as a new pipeline, ignoring
|
||||
the origin's version number and refusing an existing destination name; the
|
||||
confirmation shows the destination. Retained source and origin metadata stay
|
||||
unchanged. For an edit draft, CLI `submit --expected-version N` can explicitly
|
||||
approve an update against version N on the destination (or `--force` can explicitly
|
||||
skip that version check). For unnamed drafts, submission asks you to
|
||||
type a pipeline name directly in the TUI. Enter saves the name in retained metadata
|
||||
and opens publication confirmation; it does not publish yet. Esc keeps the draft
|
||||
without saving unfinished name input. Draft selection/editor completion never publishes it.
|
||||
|
||||
Reference in New Issue
Block a user