fix(e2e): Use consistent date for E2E tests

[jeremyckahn]

What this PR does

This PR prevents time-based events (such as for the months of October or December) from interfering with and breaking end-to-end tests.

How this change can be validated

Verify that the E2E tests pass.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
farmhand	Ready	Preview	Comment	Oct 1, 2025 1:24pm

[gemini-code-assist]

Summary of Changes

Hello @jeremyckahn, I'm Gemini Code Assist¹! 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 flakiness in end-to-end tests by ensuring a consistent date is used during test execution. By fixing the date, it prevents time-dependent features, such as seasonal events, from inadvertently breaking tests and improves the overall stability and reliability of the test suite.

Highlights

• Consistent Date for E2E Tests: Implemented a fixed date ('2025-01-01T09:00:00') for end-to-end tests to prevent time-based events from causing test failures and ensure consistent test results.

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.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

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. ↩

[gemini-code-assist]

Code Review

This pull request effectively addresses the issue of time-based events causing flakiness in end-to-end tests by setting a consistent date using Playwright's page.clock.install. The change is well-contained and the approach is solid. I've added one minor suggestion to simplify the code and improve maintainability. Overall, great work on making the tests more robust!