chore: update copyright year to 2025

[posquit0]

Summary

• Updated copyright year in README.md from "2023" to "2023-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 is a documentation update that modifies the copyright information within the project's README.md file. The change ensures the copyright year accurately reflects the ongoing period, without introducing any functional changes to the codebase.

Highlights

• Copyright Year Update: The copyright year in the README.md file has been updated from "2023" to "2023-2025" to reflect the current period.

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 README.md. While the intent to keep the copyright notice current is good, the proposed range 2023-2025 is unconventional. I have provided a suggestion to align with the standard practice, which is to use a range from the creation year to the year of the last modification. This ensures the copyright notice remains accurate over time.

[gemini-code-assist]

The standard practice for copyright year ranges is to use the creation year and the year of the last modification (e.g., 2023-2024). This ensures the copyright notice accurately reflects the period during which the work was developed. Using a projected year range is unconventional. It's better to update the end year annually as part of maintenance.

Suggested change

	Copyright © 2023-2025, [Byungjin Park](https://www.posquit0.com).
	Copyright © 2023-2024, [Byungjin Park](https://www.posquit0.com).