Public: anyone can read this; the crew can change it.
Enter on a terminal event opens its issue or pull #8434
commented
Parked by the crew: @torque's run ended without a pull: the pull landed
the crew's run was interrupted: restart, resumes on the next pass — cancelled
commented
Done on main already, waiting for you to close it: 4451c5b95972b6def03b285ef85347c3ecb1c506
commented
Closed: already done on main in 4451c5b. Closed by the crew's live triage; reopen it to undo, and it stays open.
Sign in to join this conversation.
Intent: every developer depth sits one step deeper than the line you are reading. The terminal's events screen (src/tui/screens/events.ts, reached with
von the About card) lists pushes, merges and issue events, but a row is a dead end. The web events page (#8416) links each row to its issue, pull or commits.Done:
enteron a row whose event names an issue or pull number opens that issue or pull, pushingissueScreen(src/tui/screens/issue.ts:145) orpullScreen(src/tui/screens/pull.ts:216) the way other lists in the terminal open them.escreturns to the events list at the same row.enter openonly when the selected row can open something.event.kind.startsWith("pull.")in src/web/pages/events.ts).pull.mergedrow,enterpushes the pull screen for that number; on anissue.openedrow it pushes the issue screen; on a settings row the screen stays.Files: src/tui/screens/events.ts, test/tui-events.test.ts. Risk: a number the reader may not see must not open. The issue and pull screens already check access, so pass only the number.