chore: update copyright year to 2025

[posquit0]

Summary

• Updated copyright year in README.md from "2022-2023" to "2022-2025"

Test plan

• Verify README.md displays updated copyright information
• No functional changes, documentation only

[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 primarily focuses on a minor documentation update to ensure the copyright information is current. It's a non-functional change that updates the copyright year in the project's README.md file, aligning it with the ongoing year.

Highlights

• Copyright Year Update: The copyright notice in README.md has been updated to reflect the year 2025, changing from "2022-2023" to "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 updates the copyright year in the README.md. The change is straightforward, but I've included a suggestion regarding the manual process of updating the year. To improve long-term maintainability, it would be beneficial to automate this task, for instance, by using a GitHub Action to handle annual updates. This would eliminate the need for manual pull requests for this purpose in the future.

[gemini-code-assist]

To improve maintainability and avoid manual updates each year, consider automating the copyright year update. A GitHub Action could be set up to run annually, which would automatically create a pull request with the current year. This ensures the copyright is always up-to-date without manual effort.