Remove the byline from the RE API Fellow post - #2754
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This comment has been minimized.
This comment has been minimized.
corcillo
approved these changes
Sep 8, 2026
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
2 participants
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.
What and why
Removes the author byline from the top of the RE API Fellow announcement so the post opens directly with its first paragraph. Requested after the post went live in #2749; the post should carry no byline.
How was this verified?
Ran vale on the post with zero errors. Loaded the post through the site's post loader and confirmed it still parses as the newest post with an unchanged excerpt, since the excerpt never included the byline. Not rendered in a full site build.
Risk
Low. A two-line deletion in one blog post. If wrong, the post reads oddly on the public blog, which the authors would notice first. No config, code, or API changes.
This change is