hosted:node:branch
Create one branched node and one lineage relation from the source, copying the source's title. Without --repository-id the server places it in the source's repository when you hold a write role there, otherwise in your fork of that repository, where the node starts private unless you have added members to that fork. With --repository-id, commit it in that hosted repository, which must hold the source.
Reference for flywheel hosted:node:branch.
Create and commit one branched node that copies the source's title. Without --repository-id, the server chooses the repository: the source's repository when you hold a write role there, otherwise your fork of that repository, where the node starts private unless you have added members to that fork. The result names the node, the repository it landed in and the placement. With --repository-id, the branch is committed in that hosted repository, which must already hold the source and requires a sufficient repository role. An existing repository refuses insufficient membership with 403 repository_forbidden (CLI exit 3). To add your own node under a readable parent without joining its repository, run flywheel hosted:node:create --parent <node_id> --title 'My addition'; without a write role there, it lands in your fork. Missing and unreadable sources still return 404, and nothing is created. See Add to a graph you don't own for the server-placement workflow.
Command Group
Hosted Repository
Summary
Create one branched node and one lineage relation from the source, copying the source's title. Without --repository-id the server places it in the source's repository when you hold a write role there, otherwise in your fork of that repository, where the node starts private unless you have added members to that fork. With --repository-id, commit it in that hosted repository, which must hold the source.
Usage
flywheel hosted:node:branch [FLAGS] <node_id>Arguments
| Argument | Required | Choices | Description |
|---|---|---|---|
<node_id> | Yes | Node UUID. |
Required flags
None.
Optional flags
| Flag | Value | Default | Choices | Description |
|---|---|---|---|---|
--repository-id | string | Hosted repository UUID to commit to. Omit it to let the server choose the repository. | ||
--message | string | Hosted commit message. Only with --repository-id. | ||
--expected-head | string | Expected hosted head; skips the automatic head read. Only with --repository-id. | ||
--format | FORMAT | json, tsv, csv, table | Output format for command results. | |
--env | PROFILE | Use a configured CLI profile for this invocation. | ||
--out | PATH | Write output to a file path, or use - for stdout. | ||
--open | Open browser-bound URLs when supported. | |||
--no-retry | Disable transient-error retries. | |||
--retry-max | N | Maximum transient-error retry attempts. | ||
--wait | Block on async operations until a terminal state is reached. | |||
--wait-timeout | SECONDS | 600 | Seconds to wait for --wait before timing out. Defaults to 600. | |
--allow-self | Allow mutating the currently active credential. | |||
--timeout | SECONDS | Set the per-request timeout budget in seconds. | ||
--idempotency-key | KEY | Reuse an Idempotency-Key so ambiguous write failures can be retried with the same key. | ||
--force | Force safety-gated operations where supported. | |||
--yes | Skip confirmation prompts for destructive operations. | |||
--debug | Print structured request debugging with secrets masked. | |||
--verbose | Print verbose progress for long-running operations. | |||
-h, --help | Show this help. |
Examples
Branch a node you can read; the branch lands in the source's repository or in your fork of it.
flywheel hosted:node:branch <node_id> --format=jsonCommit one branched node in this hosted repository and one lineage relation copying the source's title.
flywheel hosted:node:branch --repository-id=<uuid> <node_id> --format=jsonhosted:node-tag:remove
Commit removing a tag from a node.
hosted:node:create
Create a node from --title or the full six-field JSON values file. Without --repository-id the server places it: under --parent, in the parent's repository when you hold a write role there, otherwise in your fork of that repository, where the node starts private unless you have added members to that fork; with no --parent, as a root in your default workspace. With --repository-id, commit a root node in that hosted repository.