Skip to content
quarry Check-in [30fb5af0aa]
Login

Check-in [30fb5af0aa]

Overview
Comment:merge cross-repo tickets with trunk
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: 30fb5af0aac527fb732c00f44084570dfbbe2f03b681f7b6108169db3dc76eee
User & Date: dmestas on 2026-08-23 01:10:44.170
Other Links: manifest | tags
Context
2026-08-23
01:21
dashboard: what needs you, then where to go, then what changed

Leads with the tickets somebody else answered and left with you, which needs no stored last-seen. Two columns, not three: the third was the feed filtered to one author. The feed's kind chips count exactly the rows they show. check-in: 837a5c908a user: dmestas tags: trunk

01:10
merge cross-repo tickets with trunk check-in: 30fb5af0aa user: dmestas tags: trunk
01:10
tickets: one tracker page across every repository

/tickets is the same report machinery pointed at all granted trackers: repository becomes a browse axis, rows carry their own repo, and the board and New button stay behind since neither has one repo to mean. check-in: 94a2276f2c user: dmestas tags: trunk

01:05
merge doc-links: relative document links, doc images, entity fix check-in: ef1774989d user: dmestas tags: trunk
Changes