@ravshansbox/pi-next-issue 6.3.4 → 6.3.6
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 +1 -1
- package/package.json +1 -1
- package/skills/create-issue/SKILL.md +1 -1
package/README.md
CHANGED
|
@@ -43,7 +43,7 @@ The package ships the `create-issue` skill. Ask pi to write an issue, ask for a
|
|
|
43
43
|
1. restates the problem, reads the code when the problem touches it, and finds the open issues that must be done first;
|
|
44
44
|
2. judges whether the change fits one atomic commit that leaves the trunk green. When it is too big for one atomic commit, it proposes a split into issues that each land alone and keep the trunk green;
|
|
45
45
|
3. asks numbered questions until none is open, including whether you confirm the split;
|
|
46
|
-
4. creates the `status:todo` label with `gh label create` when the repository does not have it, then runs `gh issue create --body-file` with the body from [`template.md`](skills/create-issue/template.md) and the `status:todo` label, without showing the body first;
|
|
46
|
+
4. creates the `status:todo` label with `gh label create` when the repository does not have it, then runs `gh issue create --body-file` with the body from [`template.md`](skills/create-issue/template.md) and the `status:todo` label and no other label, without showing the body first;
|
|
47
47
|
5. links each blocker with `gh issue edit --add-blocked-by`, so the worker waits for it. For a confirmed split, it creates each issue in turn and links it to the issues of the split it depends on;
|
|
48
48
|
6. gives you the issue url and asks once whether to start a run, leave it or change it, and changes it with `gh issue edit --body-file` or `--title` until you start a run or leave it;
|
|
49
49
|
7. calls `next_issue_start` when you asked for a run.
|
package/package.json
CHANGED
|
@@ -19,7 +19,7 @@ Turn the problem of the user into one GitHub issue, or a split of linked issues
|
|
|
19
19
|
gh label create status:todo
|
|
20
20
|
```
|
|
21
21
|
|
|
22
|
-
Then create the issue without showing the body first:
|
|
22
|
+
Then create the issue without showing the body first. Add no label other than `status:todo`:
|
|
23
23
|
|
|
24
24
|
```bash
|
|
25
25
|
gh issue create --title "<title>" --body-file <file> --label status:todo
|