Repository navigation
Conversation
Share marker, headline, and body slots across activity and comment controllers. Keep pairing, deduplication, and grouping data-only; the issue feed selects its controllers and accepts optional bodies keyed by representative activity ID. Allow standalone feeds to choose composer placement. Existing issue details keep their default content, comment mutations, and composer position. Co-authored-by: Codex <codex@openai.com>
cvxluo
force-pushed
the
cvxluo/prepare-timeline-entries-and-share-row-composition
branch
from
October 16, 2026 16:19
9de4cb6 to
f37cf89
Compare
Contributor
Story previewsPreview the stories changed in this PR on the Vercel deployment:
Preview deployment: https://sentry-50lxxk0y8.sentry.dev |
This branch was successfully deployed
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
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.
Resolve comment and card bodies on prepared feed entries after activity pairing, deduplication, and status rollups. Render them through a shared TimelineItem frame while comment controllers retain editing and actions.
Allow standalone feeds to choose composer placement. Existing issue details keep their default rendering and composer position.