[T3065] FIX: last contact date is now correct#309
Conversation
Danielgergely
commented
Mar 24, 2026
- FIX: the last contact date is now the create_date of the latest correspondence (not write_date)
- FIX: the last contact date is now the create_date of the latest correspondence (not write_date)
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request addresses a bug where the 'Last contact' date shown for children was incorrectly using the modification date of the latest correspondence. The change ensures that the displayed date accurately represents when the latest correspondence was originally created, providing a more precise and meaningful contact history. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request changes the 'last contact' date display to use the create_date of the latest correspondence instead of write_date. This aligns with the stated goal of showing the creation date of the correspondence, which is more accurate than the last modification date. The change is confined to the template and appears correct based on the provided context. No issues were found during the review.