@biffo/cli 0.283.3 → 0.284.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/_skeletons/plugin-template/AGENTS.md +18 -3
- package/_skeletons/sibling-template/AGENTS.md +18 -3
- package/dist/index.js +424 -178
- package/package.json +1 -1
- package/scripts/claim.sh +119 -9
|
@@ -48,9 +48,23 @@ This file is distributed by the template and kept in step by
|
|
|
48
48
|
**Before starting work on an issue, run:**
|
|
49
49
|
|
|
50
50
|
```bash
|
|
51
|
-
sh scripts/biffo.sh claim <issue-number> [-R owner/repo]
|
|
51
|
+
sh scripts/biffo.sh claim <issue-number> --as <token> [-R owner/repo] # 0 free · 1 taken · 2 cannot tell
|
|
52
|
+
sh scripts/biffo.sh claim <issue-number> --release <token> # only the holder may clear it
|
|
52
53
|
```
|
|
53
54
|
|
|
55
|
+
**`--as <token>` is required, and there is no untokened form** (biffo-template#1562).
|
|
56
|
+
The token is opaque, identifies a **session** rather than a person, and is not a
|
|
57
|
+
secret — it appears in a public comment. Shape it `<what>-<MMDD>-<unique>`, e.g.
|
|
58
|
+
`tpl-groom-0813-9f2a`; anything with two `-`-separated parts and 6+ characters
|
|
59
|
+
is accepted, and a role word every session would share (`agent`, `bot`, `me`) is
|
|
60
|
+
refused. Omit the flag and the refusal prints a ready-made token derived from
|
|
61
|
+
your branch, so the fix is one line to copy.
|
|
62
|
+
|
|
63
|
+
Every session on a workstation claims under the same GitHub actor, so a claim
|
|
64
|
+
with no token cannot be told from a stranger's — and the rule you correctly
|
|
65
|
+
follow is _never steal a fresh claim_. Give the same token to every agent you
|
|
66
|
+
dispatch onto the issue.
|
|
67
|
+
|
|
54
68
|
Several agent sessions run against this estate at once. The script asks four
|
|
55
69
|
questions, because the answer lives in more than one place: does the issue carry
|
|
56
70
|
the `in-progress` label, is there an **open PR** referencing it, is there a
|
|
@@ -72,8 +86,9 @@ every other machine; the pushed branch is the only signal they can see. The
|
|
|
72
86
|
window between starting and pushing is where collisions actually happen — one of
|
|
73
87
|
that morning's issues went from branch to **merged in three minutes**.
|
|
74
88
|
|
|
75
|
-
**Release what you claim
|
|
76
|
-
|
|
89
|
+
**Release what you claim** — `claim <issue-number> --release <token>`, which
|
|
90
|
+
refuses to clear anybody else's. Release when the PR merges, when you close the
|
|
91
|
+
issue, or when you stop — including when you stop because someone else got
|
|
77
92
|
there first. A claim you never release is worse than no claim, because the next
|
|
78
93
|
session believes it. Before skipping something because it is claimed, check how
|
|
79
94
|
old the claim is: no activity for over an hour probably means abandoned. Steal
|
|
@@ -48,9 +48,23 @@ This file is distributed by the template and kept in step by
|
|
|
48
48
|
**Before starting work on an issue, run:**
|
|
49
49
|
|
|
50
50
|
```bash
|
|
51
|
-
sh scripts/biffo.sh claim <issue-number> [-R owner/repo]
|
|
51
|
+
sh scripts/biffo.sh claim <issue-number> --as <token> [-R owner/repo] # 0 free · 1 taken · 2 cannot tell
|
|
52
|
+
sh scripts/biffo.sh claim <issue-number> --release <token> # only the holder may clear it
|
|
52
53
|
```
|
|
53
54
|
|
|
55
|
+
**`--as <token>` is required, and there is no untokened form** (biffo-template#1562).
|
|
56
|
+
The token is opaque, identifies a **session** rather than a person, and is not a
|
|
57
|
+
secret — it appears in a public comment. Shape it `<what>-<MMDD>-<unique>`, e.g.
|
|
58
|
+
`tpl-groom-0813-9f2a`; anything with two `-`-separated parts and 6+ characters
|
|
59
|
+
is accepted, and a role word every session would share (`agent`, `bot`, `me`) is
|
|
60
|
+
refused. Omit the flag and the refusal prints a ready-made token derived from
|
|
61
|
+
your branch, so the fix is one line to copy.
|
|
62
|
+
|
|
63
|
+
Every session on a workstation claims under the same GitHub actor, so a claim
|
|
64
|
+
with no token cannot be told from a stranger's — and the rule you correctly
|
|
65
|
+
follow is _never steal a fresh claim_. Give the same token to every agent you
|
|
66
|
+
dispatch onto the issue.
|
|
67
|
+
|
|
54
68
|
Several agent sessions run against this estate at once. The script asks four
|
|
55
69
|
questions, because the answer lives in more than one place: does the issue carry
|
|
56
70
|
the `in-progress` label, is there an **open PR** referencing it, is there a
|
|
@@ -72,8 +86,9 @@ every other machine; the pushed branch is the only signal they can see. The
|
|
|
72
86
|
window between starting and pushing is where collisions actually happen — one of
|
|
73
87
|
that morning's issues went from branch to **merged in three minutes**.
|
|
74
88
|
|
|
75
|
-
**Release what you claim
|
|
76
|
-
|
|
89
|
+
**Release what you claim** — `claim <issue-number> --release <token>`, which
|
|
90
|
+
refuses to clear anybody else's. Release when the PR merges, when you close the
|
|
91
|
+
issue, or when you stop — including when you stop because someone else got
|
|
77
92
|
there first. A claim you never release is worse than no claim, because the next
|
|
78
93
|
session believes it. Before skipping something because it is claimed, check how
|
|
79
94
|
old the claim is: no activity for over an hour probably means abandoned. Steal
|