sneak, 2026-09-29 in chat (verbatim), right after #348 about expanding and collapsing events in the log viewer:
by default only the top webhook should be expanded. the rest should be collapsed. the event log should only show the 50 most recent events too.
Reading taken (the message follows the log-viewer one): "top webhook" is the top, newest event in the event log. If the page shows something else that expands per webhook, the same rule applies there: only the top one open.
Definition of done, on the event log viewer:
When the page loads, only the top (newest) event is expanded; every other event is collapsed.
The log shows the 50 most recent events, newest first, limited in the database query.
Tests cover the 50-event limit and that only the first event is expanded on load.
Model: opus-5-5
sneak, 2026-09-29 in chat (verbatim), right after https://git.eeqj.de/sneak/webhooker/issues/348 about expanding and collapsing events in the log viewer:
> by default only the top webhook should be expanded. the rest should be collapsed. the event log should only show the 50 most recent events too.
Reading taken (the message follows the log-viewer one): "top webhook" is the top, newest event in the event log. If the page shows something else that expands per webhook, the same rule applies there: only the top one open.
Definition of done, on the event log viewer:
- When the page loads, only the top (newest) event is expanded; every other event is collapsed.
- The log shows the 50 most recent events, newest first, limited in the database query.
- Expanding and collapsing still work as in https://git.eeqj.de/sneak/webhooker/issues/348.
- Tests cover the 50-event limit and that only the first event is expanded on load.
Model: opus-5-5
clawbot
self-assigned this 2026-09-29 11:36:00 +02:00
Plan. Runs after #348 lands, on the same view (templates/source_logs.html and its handler in internal/handlers/source_management.go, which paginates today with paginationPerPage).
Expanded on load: only the first (newest) event starts expanded, using the per-row state from 348.
Limit: 50 most recent events, limited in the query. If the pagination that exists today would then show pages beyond 50 events, remove it or cap it, and say which on the PR.
Styling:static/css/tailwind.css is the compiled Tailwind stylesheet and is committed. A class the page uses must already be in that file. If it is not, prefer a small plain rule in static/css/style.css. Regenerate tailwind.css only through make css, and disclose it on the PR if you do (the unpinned tool is #231).
Browser checks: headless Chrome in a container, with a small data set built in batches (the standing RAM cap), the container named with webhooker and your role, removed afterwards. Publish no screenshots or logs on the tracker.
Model: opus-5-5
Plan. Runs after https://git.eeqj.de/sneak/webhooker/issues/348 lands, on the same view (`templates/source_logs.html` and its handler in `internal/handlers/source_management.go`, which paginates today with `paginationPerPage`).
- **Expanded on load:** only the first (newest) event starts expanded, using the per-row state from 348.
- **Limit:** 50 most recent events, limited in the query. If the pagination that exists today would then show pages beyond 50 events, remove it or cap it, and say which on the PR.
- **Styling:** `static/css/tailwind.css` is the compiled Tailwind stylesheet and is committed. A class the page uses must already be in that file. If it is not, prefer a small plain rule in `static/css/style.css`. Regenerate `tailwind.css` only through `make css`, and disclose it on the PR if you do (the unpinned tool is https://git.eeqj.de/sneak/webhooker/issues/231).
- **Browser checks:** headless Chrome in a container, with a small data set built in batches (the standing RAM cap), the container named with `webhooker` and your role, removed afterwards. Publish no screenshots or logs on the tracker.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
sneak, 2026-09-29 in chat (verbatim), right after #348 about expanding and collapsing events in the log viewer:
Reading taken (the message follows the log-viewer one): "top webhook" is the top, newest event in the event log. If the page shows something else that expands per webhook, the same rule applies there: only the top one open.
Definition of done, on the event log viewer:
Model: opus-5-5
Plan. Runs after #348 lands, on the same view (
templates/source_logs.htmland its handler ininternal/handlers/source_management.go, which paginates today withpaginationPerPage).static/css/tailwind.cssis the compiled Tailwind stylesheet and is committed. A class the page uses must already be in that file. If it is not, prefer a small plain rule instatic/css/style.css. Regeneratetailwind.cssonly throughmake css, and disclose it on the PR if you do (the unpinned tool is #231).webhookerand your role, removed afterwards. Publish no screenshots or logs on the tracker.Model: opus-5-5