Skip to content

fix(web): link-coloured chat links, repository lane row, faded thread titles - #2279

Merged
chuks-qua merged 3 commits into
mainfrom
fix/thread-overview-links
Oct 21, 2026
Merged

chuks-qua merged 3 commits into
mainfrom
fix/thread-overview-links

Conversation

@chuks-qua

@chuks-qua chuks-qua commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor

What

Three display fixes for the chat and the thread view.

Chat links. Links in chat prose used the amber primary colour, shortened bare GitHub URLs to owner/repo#n, and ended with an external-link icon. They now use the blue link colour from DESIGN.md and show the URL exactly as written. The site favicon still comes before the link, so GitHub links lead with the GitHub mark.

Repository in the overview. The repository had its own "Repository" section with an amber heading and an external-link icon. It is now one lane row with the GitHub mark and owner/repo. It sits below the Commit row and above the pull request rows. Clicking it still opens the remote.

Thread titles. When a thread had no explicit title, the server took the first line of the message and cut it at 60 characters with a literal .... The header then showed that ellipsis instead of fading the text. The server now keeps up to 200 characters, cuts at a word boundary, and adds no ellipsis. The header already fades text that overflows.

Verified with focused Vitest runs (web: 4 files, 56 tests; server: thread-title.test.ts, 4 tests), tsc --noEmit for apps/web and apps/server, and bun run lint. I also checked the web app against the fixture repository, with a GitHub remote added.

Why

Links should look like links. Amber is reserved for primary actions, so amber links looked like buttons. A one-row repository entry also fits the rest of the overview lane. The title ellipsis broke the rule that text fades at the right edge and never ends in an ellipsis.

UI Changes

Chat link. Target, then after.

Target chat link
After chat link

Overview repository row. Before, then after.

Before repository section
After repository lane row

Thread header. Before, then after.

Before header ellipsis
After header fade

Review Notes

  • Threads created before this change keep their stored titles, so existing titles that end in ... still show the ellipsis. This PR does not include a migration.
  • The after capture shows the repository row under the branch row. A Direct thread has no Commit or pull request row. The order between those rows comes from OVERVIEW_ENTRIES (commit 80, repository 95, pull request 110), and overview-registry.test.tsx covers it.
  • Showing bare URLs in full drops the old owner/repo#n shortening. Authored link text was never rewritten and is still not rewritten.

View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need.

Chat links used the amber primary colour, a trailing external-link icon, and rewrote bare URLs to owner/repo#n. DESIGN.md reserves amber for primary actions and gives links the link colour. Links now show the site mark and the URL as written.
The repository had its own headed section in the activity block. It now renders as a lane row between Commit and the pull request, styled like its neighbours.
titleFrom cut the first line at 50 characters and appended '...', so headers showed a literal ellipsis instead of the fade-out truncation. Titles now keep up to 200 characters, cut at a word boundary, and clients fade the overflow.
@chuks-qua
chuks-qua merged commit 11e84a3 into main Oct 21, 2026
11 checks passed
@chuks-qua
chuks-qua deleted the fix/thread-overview-links branch October 21, 2026 16:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant