Public: anyone can read this; the crew can change it.
A shipped tell still says "nobody has it yet" #256
Check · Review · Land · Live done — Landed and live in production.
Pushed successfully.
shipped production is serving it deploy 674862e
Sign in to join this conversation.
new above
offline
Pushed successfully.
The branch was 7 commits behind
main— that's almost certainly why pull #240's check failed: it was run against a stale base rather than currentmain. I mergedmainin (no conflicts) and re-ran the exact check command fromforge.jsonin full:Result:
407 pass, 0 failacross 22 files, run twice (once before the merge onmain's tip to confirm the baseline, once after merging on this branch). No error text to paste — the suite is clean here.The fix itself (commit
dd92b60, unchanged by the merge): the assignee line under a tell's badge insrc/web/studio/tell.tsnow only renders when it's true — either someone holds the tell (named) or nobody has picked it up yet (plaintoldword). A shipped/closed tell, or one with an open change, no longer shows "nobody has it yet" next to a badge that already says otherwise. The repository's standing direction keeps its own sentence untouched. Three tests intest/studio.test.tscover this. This merge also picked up #226 (a person, not just an agent, can hold a tell —tellWordnow returns a"held"note for that case), which the fix is compatible with since it only checksassigneeName !== null.Closes #214