@brokkai/issue-bot-darwin-x64 0.3.0 → 0.4.0
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/BUILD.json +1 -1
- package/README.md +51 -7
- package/bin/bib +0 -0
- package/package.json +1 -1
package/BUILD.json
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
{"commit": "
|
|
1
|
+
{"commit": "086418e7d4706a329a2e40d49060c4dbfef026a9", "tag": "v0.4.0", "target": "darwin-amd64"}
|
package/README.md
CHANGED
|
@@ -53,6 +53,7 @@ bib --agent your-acp-agent --agent-arg=--stdio
|
|
|
53
53
|
bib --claim-timeout 15m
|
|
54
54
|
bib --draft=false
|
|
55
55
|
bib status
|
|
56
|
+
bib version
|
|
56
57
|
bib retry --issue 123 --once
|
|
57
58
|
```
|
|
58
59
|
|
|
@@ -62,6 +63,46 @@ prints saved JSON without starting an agent. `retry` resets pending/blocked
|
|
|
62
63
|
attempt budgets and resumes work; `--issue` restricts it to that issue. Run
|
|
63
64
|
`bib --help` for all flags.
|
|
64
65
|
|
|
66
|
+
`bib version` prints the embedded release tag. Local builds report `dev`; binaries installed with `go install ...@version` report the module version.
|
|
67
|
+
|
|
68
|
+
## Terminal dashboard
|
|
69
|
+
|
|
70
|
+
Interactive runs show the same live dashboard as bug-bot. It fits the current
|
|
71
|
+
terminal or tmux pane and adjusts when resized. Each pane runs one repository.
|
|
72
|
+
|
|
73
|
+
```sh
|
|
74
|
+
bib /path/to/repo # live dashboard
|
|
75
|
+
bib /path/to/repo --plain # scrolling logs and agent transcript
|
|
76
|
+
bib /path/to/repo --json # structured logs
|
|
77
|
+
```
|
|
78
|
+
|
|
79
|
+
The overview shows the repository, branch and active base commit, issue task,
|
|
80
|
+
active tool, uptime, attempt budget, and next poll countdown. Larger panes also
|
|
81
|
+
show the selected model and reasoning effort. Saved counts cover all recorded
|
|
82
|
+
jobs: issues, submitted PRs, existing PRs, pending, blocked, and skipped. A PR is
|
|
83
|
+
counted as submitted only after confirmation; restored jobs remain in the totals.
|
|
84
|
+
|
|
85
|
+
The issue browser shows up to 200 saved jobs ordered by issue number, including
|
|
86
|
+
the active issue. Details include the issue, branch, result, test evidence,
|
|
87
|
+
failure, retry eligibility, and PR link. Run counters track PRs completed during
|
|
88
|
+
this invocation, attempts, agent starts, tools, and error log events.
|
|
89
|
+
|
|
90
|
+
- `1`, `2`, `3` or `Tab`: switch overview, issues, and activity.
|
|
91
|
+
- `↑` / `↓` or `k` / `j`: browse results or scroll activity.
|
|
92
|
+
- `Enter`: inspect the selected result. `Esc`: return to the list.
|
|
93
|
+
- `Page Up` / `Page Down`: scroll details. `g` / `G`: jump to start/end;
|
|
94
|
+
`G` resumes following live activity.
|
|
95
|
+
- `q` or `Ctrl+C`: stop the bot and its agent, save progress, and restore the terminal.
|
|
96
|
+
|
|
97
|
+
Activity keeps recent output; full agent transcripts remain in the state
|
|
98
|
+
directory. On exit, a summary and changed result links stay in the terminal.
|
|
99
|
+
`once` exits when its check or attempt finishes.
|
|
100
|
+
|
|
101
|
+
Piped input, redirected stderr, and `TERM=dumb` automatically use scrolling
|
|
102
|
+
output. `--plain` and `--json` disable the dashboard and are mutually exclusive.
|
|
103
|
+
`NO_COLOR` disables colors. `status`, `version`, and help retain their existing
|
|
104
|
+
output and never open the dashboard.
|
|
105
|
+
|
|
65
106
|
## How it works
|
|
66
107
|
|
|
67
108
|
1. Walk all open, unlocked issues, oldest first, with pagination. No label
|
|
@@ -205,13 +246,16 @@ data in the agent instructions, not as permission to broaden the task.
|
|
|
205
246
|
|
|
206
247
|
## Publishing npm packages
|
|
207
248
|
|
|
208
|
-
|
|
209
|
-
|
|
210
|
-
|
|
211
|
-
|
|
212
|
-
|
|
213
|
-
|
|
214
|
-
|
|
249
|
+
Pushing a `v*` version tag automatically runs CI, publishes the native GitHub
|
|
250
|
+
release, and uploads the four npm platform packages followed by the launcher.
|
|
251
|
+
Follow the **Publish packages** workflow for the complete pipeline; it keeps all
|
|
252
|
+
artifacts tied to the same tag and commit. No separate manual dispatch is needed.
|
|
253
|
+
|
|
254
|
+
The manual workflow remains available for recovery: dispatch from the existing
|
|
255
|
+
tag with its tag input and `publish=true`, or use `publish=false` for validation
|
|
256
|
+
only. Existing package bytes are checked for conflicts before uploading.
|
|
257
|
+
Successful uploads do not wait for npm's public version index or run immediate
|
|
258
|
+
public-install checks. Use the explicit registry `verify` command later if needed.
|
|
215
259
|
|
|
216
260
|
The workflow uses the `packages-publish` environment. Configure npm trusted
|
|
217
261
|
publishing for each of the five `@brokkai/issue-bot*` packages with repository
|
package/bin/bib
CHANGED
|
Binary file
|
package/package.json
CHANGED