Fix assignment event time inconsistency with GitHub.com #7061
+0
−1
Conversation
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
Co-authored-by: alexr00 <38270282+alexr00@users.noreply.github.com>
Copilot
AI
changed the title
Copilot finished work on behalf of
alexr00
June 23, 2025 15:09
Co-authored-by: alexr00 <38270282+alexr00@users.noreply.github.com>
Done. Removed the comment in 3df9ee2. |
Copilot finished work on behalf of
alexr00
June 24, 2025 09:51
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.
When multiple assignment/unassignment events happen within 10 minutes by the same actor, VSCode consolidates them into a single timeline item. However, VSCode was showing the most recent time while GitHub.com shows the earliest time, causing confusion for users.
Before:
After:
The fix removes the line that was updating the consolidated event's timestamp to the newest time, instead keeping the original (earliest) timestamp to match GitHub.com's behavior.
Technical Details:
In
webviews/components/timeline.tsx, when consolidating assignment events that occur within 10 minutes by the same actor, the code was settinglastEvent.createdAt = newEvent.createdAtwhich used the most recent time. This line has been removed so the earliest time is preserved.Fixes #7007.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.