Repository navigation
Description
Problem
GitHub allows readers to inspect the edit history of a comment, including earlier versions and changes between revisions:
https://docs.github.com/en/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment
T3 Code currently displays the latest comment content but does not offer an equivalent way to inspect prior revisions in its web, desktop, or mobile clients. When a GitHub comment is edited, readers cannot review the earlier wording without leaving T3 Code.
Expected behavior
For GitHub issue and pull request comments, including inline review comments wherever GitHub exposes edit history:
- Indicate that a comment has been edited using T3 Code's existing comment design conventions.
- Provide a discoverable View edit history action on edited comments.
- Show the available revisions in chronological order, including editor and timestamp when available.
- Allow readers to inspect prior contents and compare revisions with a readable diff.
- Return to the current comment without losing the current reading position.
- Provide equivalent functionality in web, desktop, and mobile, with platform-appropriate controls.
- Respect GitHub permissions and handle unavailable histories without displaying invented versions.
Steps to reproduce
- Open a GitHub issue or pull request with a comment edited multiple times.
- Open the same issue or pull request in T3 Code.
- Try to inspect the comment's previous revisions.
Actual: T3 Code shows the latest comment content but provides no revision-history view.
Expected: T3 Code exposes the history GitHub makes available for that comment.
Scope and implementation considerations
- This requests historical comment revisions, not comment editing, refreshing the latest text, or detecting comment updates for agent notifications.
- Check which historical revisions and metadata GitHub's supported APIs actually expose. Do not reconstruct history from timestamps alone.
- Reuse the existing source-control integration and shared UI patterns, rather than introducing parallel comment storage or a synchronization service.
Related work (not duplicates)
- fix(client-runtime): refresh edited pull request comments #8094 updates the displayed comment after editing; it does not retrieve previous versions.
- fix(server): PR watch wakes the agent when a bot edits its review comment #15415 retrieves GitHub
lastEditedAtto detect edits for PR watchers, not display revision history. - PR watch reports an edited comment as a new comment on every edit #30342 and fix(server): a PR watch wakes once for a comment's edits, not on every edit #30674 address duplicate PR-watch notifications from edits, not historical-version viewing.
Acceptance criteria
- An edited GitHub comment has a discoverable edit-history action when history is available.
- Users can inspect all available historical versions, with previous text, timestamps, and editors when provided by GitHub.
- Users can compare revisions with a readable representation of changes.
- The feature is available on web, desktop, and mobile.
- Unedited comments and restricted/unavailable histories are handled gracefully, without misleading controls.
- Tests cover revision retrieval, unavailable histories, and the relevant client UI flows.
Activity
juliusmarminge commentedon Nov 22, 2026
Thanks for writing this up. It asks for new behaviour rather than reporting a defect, so it does not belong in the bug tracker and I'm closing it as not planned here. Feature ideas are discussed in Discussions: please post it there.