Update year, version, and add DOI badge to README

[abearab]

close #108

[gemini-code-assist]

Summary of Changes

Hello, 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 focuses on maintaining and enhancing the project's metadata. It updates the copyright period, improves academic discoverability by integrating a DOI badge, and ensures the project's version and author information are current and comprehensive within the pyproject.toml file. These changes collectively contribute to better project management and external referencing.

Highlights

• Copyright Year Update: The copyright year in the LICENSE file has been extended from 2024 to 2026, ensuring up-to-date legal information.
• README Badges: A new Digital Object Identifier (DOI) badge has been added to the README.md to enhance discoverability and provide a persistent link to the project's Zenodo record. The CodeQL badge was also removed.
• Project Version and Authors: The project version in pyproject.toml has been incremented from 0.5.1 to 0.6.0, and the author list has been updated with full names and an additional author for improved attribution.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• LICENSE
  • Updated the copyright year from 2022-2024 to 2022-2026.
• README.md
  • Added a new DOI badge linking to the project's Zenodo record.
  • Removed the CodeQL workflow badge.
• pyproject.toml
  • Incremented the project version from "0.5.1" to "0.6.0".
  • Updated the primary author's name and email, and added a second author.

Activity

• The pull request was opened by abearab to address issue Discuss assigning a DOI for citation #108.

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 updates the copyright year in the LICENSE file, bumps the project version and updates authors in pyproject.toml, and adds a DOI badge to the README.md while removing the CodeQL badge. My review focuses on improving configuration clarity and documentation formatting. I've suggested removing a redundant static version declaration in pyproject.toml to align with the use of dynamic versioning, which will prevent potential confusion about the package version. Additionally, I've pointed out an extra blank line in README.md that should be removed for better formatting.