Parents and children of check-in [411e60c2d5]
|
2026-08-25
| ||
| 12:01 | Suite green; merges clean. Three fixes: the events gate, the forum meta line, and the pager on narrow screens. check-in: 9c4f090ca6 user: dmestas tags: trunk | |
| 11:05 |
The event log is as public as the timeline
Every other repository page leaves visibility to the ops layer. A gateAt here made this the one page a public repository would not show an anonymous reader, while its timeline, forum and landings all did. Safe because of what is on it. The derived events restate artifacts the timeline already shows. The operational ones carry no identity at all — Counted is func(repo string, clone bool), with no user and no address anywhere in the path — so a clone event says how many, never who. check-in: 318949277b user: dmestas tags: events-public | |
|
2026-08-24
| ||
| 23:12 | land praise-ui check-in: 411e60c2d5 user: dmestas tags: trunk | |
| 23:05 | Suite green; merges clean. Already deployed — the running binary carried this while the site was down, and trunk now matches it. check-in: d8a35694f0 user: dmestas tags: trunk | |
| 21:20 |
Event log: proof the hooks fired
Read straight off the vocabulary stream — no table, no fold, nothing to keep in sync, so it cannot disagree with what the forge published. The window is the stream's window, 24 hours, and the page says so: a log that let a reader assume history would be lying about a live tail. Asks the consumer how much is pending before fetching. Without that a quiet repository waits out the fetch timeout, which would make 'nothing has happened yet' the slowest page on the site — 2s became 9ms. Linked from the webhooks settings, not given a tab: that is where the question gets asked. closed check-in: a5c5fe771e user: dmestas tags: praise-ui | |