One slot per pipe: next names each idle pipe's next item; the in-flight count counts review items by skavhaug · Pull Request #406 · expertanalytics/rasputin · GitHub
Skip to content

One slot per pipe: next names each idle pipe's next item; the in-flight count counts review items - #406

Merged
skavhaug merged 2 commits into
masterfrom
worktree-pipe-per-slot
Oct 29, 2026
Merged

skavhaug merged 2 commits into
masterfrom
worktree-pipe-per-slot

Conversation

@skavhaug

Copy link
Copy Markdown
Member

Harness item pipe-per-slot (fast lane).

  • work_pipes.py next prints one line per pipe with no item in flight, naming its next queued item; the three-place cap and lending are deleted.
  • The in-flight count counts designing, red, green and review items; items waiting on Ola do not count. Views read N of .
  • The dispatch skill says one item in flight per pipe (53 words out, 53 in).

-14 net lines. Touched suites: 914 passed, 4 xfailed.

🤖 Generated with Claude Code

skavhaug and others added 2 commits October 29, 2026 19:54
…ms count as in flight (@developer)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…s as in flight (@developer)

next prints a line for each pipe with no item in flight, naming its next
queued item; the three-place cap and its lending across pipes are gone.
An item in a step counts as in flight whether or not it has a PR or an
agent; only an item waiting on Ola does not. The recap counter reads N of
the number of pipes. The dispatch skill says one item per pipe.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@skavhaug
skavhaug enabled auto-merge October 29, 2026 19:37
@skavhaug
skavhaug added this pull request to the merge queue Oct 29, 2026
Merged via the queue into master with commit ff0d9c9 Oct 29, 2026
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant