@ravshansbox/pi-next-issue 1.1.0 → 1.2.0

package/README.md

@@ -10,13 +10,11 @@ It needs `git` and an authenticated [`gh`](https://cli.github.com/). It works wi
 
 ## Use
 
-Run these in pi, inside a git repository:
+Run this in pi, inside a git repository:
 
-- `/next-issue start` starts a run.
-- `/next-issue stop` stops the run. The issue keeps its saved state, and the next run resumes it.
-- `/next-issue status` shows where the run is.
+- `/next-issue` starts a run when none is going, and stops the run when one is going or stopping. A stopped issue keeps its saved state, and the next run resumes it.
 
-The footer shows the issue, the stage, the number of tool calls and the time spent on the issue, for example `next-issue #12 · review 1/3 · 37 tools · 4m12s`. A line above the editor shows the last tool call. In the terminal, both use the dim colour of the theme, like the rest of the footer. A note appears when an issue is merged or needs a human.
+The footer shows the issue, the stage, the number of tool calls and the time spent on the issue, for example `next-issue #12 · review 1/3 · 37 tools · 4m12s`. After a run ends, it keeps the last summary. A line above the editor shows the last tool call. In the terminal, both use the dim colour of the theme, like the rest of the footer. A note appears when an issue is merged or needs a human.
 
 The run does not belong to a session: it goes on after `/new`, `/resume`, a fork or a reload, and the new session shows it. It stops when you quit pi.
 
@@ -28,7 +26,7 @@ Each loop fetches the 200 oldest open issues with the `status:todo` label and no
 2. Add a git worktree at `.worktrees/<n>` on the `<n>` branch, from the remote default branch.
 3. The implementer agent does the work. The extension commits it, with the subject from a `commit:` line in the reply of the agent, and pushes. When a resumed issue already has a commit ahead of the base, the extension keeps it and skips the implementer.
 4. Open a pull request that closes the issue.
-5. Wait for the checks. On a red build, the fixer agent gets the failed logs, up to `maxCiFixes` times.
+5. Wait for the checks. On a red build, the fixer agent gets the failed logs. It gets at most `maxCiFixes` such fixes for the whole issue, and this count includes the checks after review fixes.
 6. The reviewer agent judges the diff and gives a verdict with `blocking` and `minor` findings, which goes on the pull request. Any change the reviewer makes is thrown away.
 7. While review rounds are left, the fixer gets every finding, and the checks and the review run again. In the last round only a blocking finding stops the merge.
 8. Squash-merge the pull request, wait until it is merged, set `status:done`, and remove the worktree, the local branch, the remote branch and the saved state.
@@ -45,11 +43,11 @@ The state of each issue is saved in `.worktrees/<n>.json`. Each loop removes the
 
 An optional `.pi/next-issue.json` in the repository sets these fields:
 
-| Field                 | Default    | Meaning                                           |
-| --------------------- | ---------- | ------------------------------------------------- |
-| `remote`              | `"origin"` | The git remote to push to.                        |
-| `maxCiFixes`          | `3`        | Fixes of red checks per issue.                    |
-| `maxReviewRounds`     | `3`        | Review rounds per issue.                          |
-| `checkTimeoutMinutes` | `30`       | The longest wait for the checks, and for a merge. |
-| `diffMaxChars`        | `60000`    | The longest diff that the reviewer gets.          |
-| `logMaxChars`         | `20000`    | The longest failed log that the fixer gets.       |
+| Field                 | Default    | Meaning                                                                           |
+| --------------------- | ---------- | --------------------------------------------------------------------------------- |
+| `remote`              | `"origin"` | The git remote to push to.                                                        |
+| `maxCiFixes`          | `3`        | Fixes of red checks for the whole issue, including the checks after review fixes. |
+| `maxReviewRounds`     | `3`        | Review rounds per issue.                                                          |
+| `checkTimeoutMinutes` | `30`       | The longest wait for the checks, and for a merge.                                 |
+| `diffMaxChars`        | `60000`    | The longest diff that the reviewer gets.                                          |
+| `logMaxChars`         | `20000`    | The longest failed log that the fixer gets.                                       |

package/index.ts

@@ -148,59 +148,39 @@ export function createExtension(launch: Launch) {
     });
 
     pi.registerCommand('next-issue', {
-      description: 'Work through the GitHub issues of this repository in the background',
-      getArgumentCompletions: (prefix) => {
-        const items = ['start', 'stop', 'status']
-          .filter((name) => name.startsWith(prefix))
-          .map((name) => ({ value: name, label: name }));
-        return items.length > 0 ? items : null;
-      },
-      handler: async (args, ctx) => {
-        const action = args.trim() || 'status';
+      description: 'Start or stop working through the GitHub issues of this repository',
+      handler: async (_args, ctx) => {
         const current = holder().runner;
         const busy =
           current?.progress.status === 'running' || current?.progress.status === 'stopping';
-        if (action === 'start') {
-          if (busy || holder().launching) {
-            ctx.ui.notify('next-issue is running already', 'warning');
-            return;
-          }
-          holder().launching = true;
-          let runner: Runner;
-          try {
-            runner = await launch(ctx.cwd);
-          } catch (error) {
-            ctx.ui.notify(
-              `next-issue cannot start: ${error instanceof Error ? error.message : String(error)}`,
-              'error',
-            );
-            return;
-          } finally {
-            holder().launching = false;
-          }
-          holder().runner = runner;
-          if (ctx.hasUI) {
-            ui = ctx.ui;
-            coloured = ctx.mode === 'tui';
-            follow(runner);
-          }
-          void runner.run();
-        } else if (action === 'stop') {
-          if (!busy) {
-            ctx.ui.notify('next-issue is not running', 'info');
-            return;
-          }
+        if (busy) {
           current?.stop();
-        } else if (action === 'status') {
+          return;
+        }
+        if (holder().launching) {
+          ctx.ui.notify('next-issue is starting already', 'warning');
+          return;
+        }
+        holder().launching = true;
+        let runner: Runner;
+        try {
+          runner = await launch(ctx.cwd);
+        } catch (error) {
           ctx.ui.notify(
-            current === undefined
-              ? 'next-issue has not run yet'
-              : formatStatus(current.progress, Date.now()),
-            'info',
+            `next-issue cannot start: ${error instanceof Error ? error.message : String(error)}`,
+            'error',
           );
-        } else {
-          ctx.ui.notify('usage: /next-issue start | stop | status', 'warning');
+          return;
+        } finally {
+          holder().launching = false;
+        }
+        holder().runner = runner;
+        if (ctx.hasUI) {
+          ui = ctx.ui;
+          coloured = ctx.mode === 'tui';
+          follow(runner);
         }
+        void runner.run();
       },
     });
   };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ravshansbox/pi-next-issue",
-  "version": "1.1.0",
+  "version": "1.2.0",
   "description": "Pi extension that works through GitHub issues in the background",
   "license": "MIT",
   "type": "module",