@ravshansbox/pi-next-issue 2.3.1 → 2.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/README.md +2 -2
- package/index.ts +0 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -14,7 +14,7 @@ Run this in pi, inside a git repository:
|
|
|
14
14
|
|
|
15
15
|
- `/next-issue` starts a run of this repository when none is going, and stops the run when one is going. A stop takes effect after the current round, and the issue keeps its saved state, so the next run resumes it.
|
|
16
16
|
|
|
17
|
-
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 · 37 tools · 4m12s`. After a run ends, it keeps the last summary.
|
|
17
|
+
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 · 37 tools · 4m12s`. After a run ends, it keeps the last summary. In the terminal, it uses the dim colour of the theme, like the rest of the footer. A note appears when an issue is done, needs a human or fails.
|
|
18
18
|
|
|
19
19
|
## Worker
|
|
20
20
|
|
|
@@ -23,7 +23,7 @@ The extension does no work itself. On `/next-issue` it connects to the `next-iss
|
|
|
23
23
|
- Every pi on the machine shares the one worker, and every pi in a repository shows the run of that repository, whoever started it.
|
|
24
24
|
- Opening pi does not start a worker. It only shows a run when a worker is going.
|
|
25
25
|
- The run does not belong to pi: it goes on after `/new`, `/resume`, a fork, a reload or quitting pi.
|
|
26
|
-
- The worker stays when every pi is closed. Stop it with `
|
|
26
|
+
- The worker stays when every pi is closed. Stop it with `npx next-issue stop`.
|
|
27
27
|
- When the extension is newer than the worker, the worker closes once no run is going, and the extension starts the newer worker.
|
|
28
28
|
|
|
29
29
|
Each run asks the worker to merge the pull requests. See the [`next-issue` README](../next-issue/README.md) for what a run does, its labels, its state and its config.
|
package/index.ts
CHANGED
|
@@ -105,8 +105,6 @@ export function createExtension(options: Options) {
|
|
|
105
105
|
}
|
|
106
106
|
const dim = (text: string) => (coloured ? ui!.theme.fg('dim', text) : text);
|
|
107
107
|
ui.setStatus(STATUS_KEY, dim(formatStatus(progress, Date.now())));
|
|
108
|
-
const active = progress.status === 'running' && progress.lastTool !== undefined;
|
|
109
|
-
ui.setWidget(STATUS_KEY, active ? [dim(`↳ ${progress.lastTool}`)] : undefined);
|
|
110
108
|
};
|
|
111
109
|
|
|
112
110
|
const onProgress = (progress: Progress | undefined) => {
|