bitfolk 0.1.8 → 0.1.10
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +6 -0
- package/dist/cli.js +69 -69
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -57,6 +57,12 @@ release rather than reuse one it cached. Installed, it also answers to the short
|
|
|
57
57
|
`bitfolk help <command>` shows a command's options. Older forms keep working: `tool add`, `tool rm`, `ls`, `doctor`,
|
|
58
58
|
`set machine`, and `run` with no words (or just an agent's name), which is `up`.
|
|
59
59
|
|
|
60
|
+
While `bitfolk up` runs on a terminal, a prompt under its status panel takes commands: type `status`, `sessions`,
|
|
61
|
+
`run "<what>"` (queued for this runner), `logs <id>`, `cancel <id>`, `approvals`, `approve <id>`, `chat`, `repos` and
|
|
62
|
+
the like, without `bitfolk` in front. Each runs as `bitfolk <command>` and its output scrolls above the panel. `help`
|
|
63
|
+
lists them, `quit` or Ctrl-C stops `up`. Commands that take over the terminal (`login`) or never end (`--follow`) stay
|
|
64
|
+
for another tab.
|
|
65
|
+
|
|
60
66
|
On a terminal, waits show a twinkling loader with the time so far, and `bitfolk up` keeps one live line under its log
|
|
61
67
|
(listening, builders working, cost so far). In a pipe, a log file, CI, or with `NO_COLOR`, `--no-color`, `TERM=dumb` or
|
|
62
68
|
`BITFOLK_NO_ANIMATION=1`, it prints plain lines only.
|