chore: update copyright year to 2025

[posquit0]

Summary

• Updated copyright year from "Copyright © 2022-2024" to "Copyright © 2022-2025" in README.md

Test plan

• Verify copyright notice is updated correctly
• Ensure no other content was modified

[gemini-code-assist]

Summary of Changes

Hello @posquit0, 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 performs a routine maintenance update to ensure the project's copyright information is current. It updates the copyright year displayed in the README.md file to the upcoming year, maintaining accuracy and compliance.

Highlights

• Copyright Year Update: The copyright notice in README.md has been updated to reflect the year 2025, changing "Copyright © 2022-2024" to "Copyright © 2022-2025".

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 correctly updates the copyright year in the README.md file. My review includes a suggestion to consider automating this annual task to improve the project's long-term maintainability. Overall, the change is good.

[gemini-code-assist]

While updating the copyright year is necessary, doing it manually each year is a recurring chore that can be forgotten, potentially leaving the project with outdated information. To improve long-term maintainability, I recommend automating this process. A common approach is to use a GitHub Action that runs on a schedule (e.g., annually) to automatically create a pull request with the updated year.