Tighten Discord announce formatting (first-sentence teaser + NimbleBrain identity)#20
Merged
Merged
Conversation
The mechanical 280-char cap produced a cluttered, pill-heavy block cut mid-sentence (CHANGELOG leads are dense with backtick identifiers). Switch to a first-sentence teaser: the opening sentence is clean prose, the code-dense detail comes later. Sentence splitting is backtick-aware so a `.` inside `tokens.bgSubtle` isn't a false boundary; a terse opener pulls in the second sentence when it fits; a 320-char word-boundary cap remains as a safety net. Also set the webhook username to "NimbleBrain Releases" so posts stop showing as "GitHub Releases" (the webhook's default identity). Avatar is set on the webhook in Discord settings.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #19. The first live post (screenshot context) was cluttered: the 280-char cap dumped the whole code-dense lead paragraph as a wall of gray pills, cut mid-sentence at "…resolved to…".
Change
First-sentence teaser instead of a char chunk. CHANGELOG leads open with clean prose; the inline-code-heavy detail comes later. Take the opening sentence (+ the second only if the first is terse and they still fit). Sentence boundaries are detected backtick-aware, so a
.insidetokens.bgSubtleis never a false split. A 320-char word-boundary cap stays as a safety net.Before → after, against the real v0.10.2 body:
Fixes three `ui` tokens... `tokens.bgSubtle`, `tokens.fgFaint`, and `tokens.borderStrong` reference CSS vars (`--color-background-tertiary`, ...) that no host injected, so they always resolved to…Fixes three `ui` tokens that were theme-blind in dark mode.Identity rebrand. Set the webhook
usernametoNimbleBrain Releasesso posts stop showing as "GitHub Releases". (The octocat avatar is the webhook's own avatar — set it in Discord → Edit Webhook to finish the rebrand; applies to all repos sharing the org webhook.)Verified (dry-run, all paths)
username: "NimbleBrain Releases".### Fixedfirst) →::warning::+ generic copy + link (unchanged).Not changed
Crossposting: the channel is a Discord Announcement channel ("Publish" prompt), and webhooks can't auto-publish — that needs the bot upgrade, tracked separately with the shared-action extraction.