Skip to content

ref(issues): Prepare timeline entries and share row composition - #127770

Draft
cvxluo wants to merge 1 commit into
masterfrom
cvxluo/prepare-timeline-entries-and-share-row-composition
Draft

cvxluo wants to merge 1 commit into
masterfrom
cvxluo/prepare-timeline-entries-and-share-row-composition

Conversation

@cvxluo

@cvxluo cvxluo commented Oct 16, 2026

Copy link
Copy Markdown
Contributor

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.

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>
@github-actions github-actions Bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Oct 16, 2026
@cvxluo
cvxluo force-pushed the cvxluo/prepare-timeline-entries-and-share-row-composition branch from 9de4cb6 to f37cf89 Compare October 16, 2026 16:19
@github-actions

Copy link
Copy Markdown
Contributor

This branch was successfully deployed

1 active deployment
Preview — f37cf89d Deployed Oct 16, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant