beady-eye v0.35.0

Every ticket called back: in beady-eye 0.35, a gate tells its bead what happens on the pull request

Cooked by agents, checked at the pass by the head chef. 21 October 2026

A bead held back by a gate on an open pull request now hears more of what happens there. In beady-eye 0.35.0, bdi gates tells it of each new head the author pushes, of every check on the head passing, of the head falling behind a base that requires up-to-date branches, and of each reply or lone inline comment in a review. Each is told once, and the gate stays open. You need do nothing to get these.

brew upgrade codeforbreakfast/tap/bdi
# or
cargo install beady-eye

The VAT line on the receipt waits until the till’s pull request #42 is approved. Nobody has approved it yet, but the cook pushed a fix, every check on it went green, the base moved on underneath, and the saucier replied to a thread. One look from bdi gates and the bead has heard all four.

Read the demo as text

spoon $ bdi gates
bdi gates: settling the gh:pr, gh:issue, gh:release, gh:run, timer and bead gates of 1 projec
t, for every owner's repositories, every 2s
greasy-spoon/till#42 has passing checks: spoon told spoon-1.2
greasy-spoon/till#42 is behind its base: spoon told spoon-1.2
greasy-spoon/till#42 was commented on inline: spoon told spoon-1.2
greasy-spoon/till#42 has a new head: spoon told spoon-1.2
^C
spoon $ bd comments spoon-1.2
Comments on spoon-1.2:
[cook] at 2026-10-21 06:14
    The checks on f1dd1e2b, the head of pull request greasy-spoon/till#42, passed.
[cook] at 2026-10-21 06:14
    The head of pull request greasy-spoon/till#42, f1dd1e2b, is behind its base, so the gh:pr
    gate waiting on it stays open.
[cook] at 2026-10-21 06:14
    saucier replied in a review thread on pull request greasy-spoon/till#42.
    https://github.com/greasy-spoon/till/pull/42#discussion_r31
[cook] at 2026-10-21 06:14
    Pull request greasy-spoon/till#42 has a new head, f1dd1e2. https://github.com/greasy-
    spoon/till/commit/f1dd1e2b
spoon $

The webhook says who rang the bell

bdi gates --listen used to treat a GitHub delivery only as a prompt to go and look again, so a label, a dismissed review or a passing check suite never reached a waiting seat. Now each delivery tells the gate’s beads what happened: who acted, and a link to what they did. It never quotes anyone’s words. The configuration guide has a table of what each delivery tells.

Inline comments at once

bdi gates --listen also settles a pull request on an inline review comment. Subscribe your webhook to Pull request review comments and a bead hears of one straight away, rather than at the next look. Without the subscription nothing changes.

Ticket’s still on the rail. You’ll hear when it moves.