Skip to content

Fix tomorrow agenda#33

Merged
chmouel merged 1 commit intochmouel:mainfrom
josecastillolema:tomorrow
Mar 23, 2026
Merged

Fix tomorrow agenda#33
chmouel merged 1 commit intochmouel:mainfrom
josecastillolema:tomorrow

Conversation

@josecastillolema
Copy link
Copy Markdown
Contributor

Tomorrow agenda (after 24h is not properly displayed as Tomorrow).
Before the fix (the event (No title) should appear as Tomorrow, but appears as Tue 24):

$ nextmeeting
• Tomorrow at 13H45 - Perf&Scale Weekly Telco Sync Up Meeting
• Tomorrow at 15H00 - Q1 26 Global Eng All Hands
• Tomorrow at 15H00 - OCP PerfScale Team Sync
• Tue 24 at 20H30 - (No title)

After the fix:

$ nextmeeting
• Tomorrow at 13H45 - Perf&Scale Weekly Telco Sync Up Meeting
• Tomorrow at 15H00 - Q1 26 Global Eng All Hands
• Tomorrow at 15H00 - OCP PerfScale Team Sync
• Tomorrow at 20H30 - (No title)

Signed-off-by: Jose Castillo Lema <josecastillolema@gmail.com>
@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello, 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 resolves a display bug in the nextmeeting tool where events occurring on the subsequent calendar day were sometimes mislabeled with a specific date (e.g., 'Tue 24') instead of the more user-friendly 'Tomorrow'. The change refines the date formatting logic to ensure that any event scheduled for the very next calendar day is consistently presented as 'Tomorrow', enhancing the readability and accuracy of the meeting agenda.

Highlights

  • Bug Fix: Corrected an issue where events scheduled for the calendar day after the current day were not always displayed as 'Tomorrow' if they were more than 24 hours away.
  • Date Calculation Logic: Modified the date comparison logic in _format_time_until to explicitly check if an event's date matches the actual calendar date of 'tomorrow', rather than relying on deltad.days == 0.
Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@chmouel
Copy link
Copy Markdown
Owner

chmouel commented Mar 23, 2026

thanks 🙏🏻

@chmouel chmouel merged commit ca199a2 into chmouel:main Mar 23, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants