Conversation
Summary of ChangesHello, I'm Gemini Code Assist1! 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 officially releases version v2026.0.0, introducing a wide array of new scientific capabilities, performance optimizations, and critical bug fixes. It also includes essential updates to contributor information and substantial improvements to user and developer documentation, streamlining the understanding and use of the project's latest features. Highlights
🧠 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
Activity
Using Gemini Code AssistThe 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
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 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
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request primarily handles a version bump to v2026, along with updates to the authors list and documentation. The changes in .mailmap and AUTHORS clean up contributor information. The documentation is improved with updated instructions for bug reporting, CI, and git usage for new contributors. New release notes for v2026 are also added. My review focuses on improving the clarity and correctness of the documentation and fixing a potential issue in the .mailmap file.
| James Wurster <jhw5@st-andrews.ac.uk> jameswurster <jameswurster@bitbucket.org> | ||
| Jean-François Gonzalez <Jean-Francois.Gonzalez@ens-lyon.fr> | ||
| Jolien Malfait <jolien.malfait@kuleuven.be> Jolien128 <72729152+Jolien128@users.noreply.github.com> | ||
| Josh Calcino <josh.calcino@gmail.com> josh <> |
There was a problem hiding this comment.
The empty email alias <> for josh is likely incorrect and might cause issues with git history parsing. It's better to remove it if there's no specific email to map.
Josh Calcino <josh.calcino@gmail.com> josh
| cat id_rsa.pub | ||
| ... some long key is printed ... | ||
|
|
||
| git clone https://github.com/USERNAME/phantom.git | ||
| If you don't have an ssh key, you can generate one using:: | ||
|
|
||
| ssh-keygen | ||
| ... follow the prompts, you can just press enter to accept the defaults ... | ||
| cat ~/.ssh/id_ed25519.pub |
There was a problem hiding this comment.
The instructions for SSH keys are a bit confusing as they mention both id_rsa.pub and then id_ed25519.pub. It would be clearer to recommend one type of key and be consistent. The ed25519 keys are more modern and secure, so I'd recommend standardizing on them. Also, it's good practice to specify the key type and a comment with ssh-keygen.
| cat id_rsa.pub | |
| ... some long key is printed ... | |
| git clone https://github.com/USERNAME/phantom.git | |
| If you don't have an ssh key, you can generate one using:: | |
| ssh-keygen | |
| ... follow the prompts, you can just press enter to accept the defaults ... | |
| cat ~/.ssh/id_ed25519.pub | |
| cat id_ed25519.pub | |
| ... some long key is printed ... | |
| If you don't have an ssh key, you can generate one using:: | |
| ssh-keygen -t ed25519 -C "your_email@example.com" | |
| ... follow the prompts, you can just press enter to accept the defaults ... | |
| cat ~/.ssh/id_ed25519.pub |
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
1 participant
Description:
Version bump to v2026, updated authors list
Components modified:
Type of change:
v2026 release
Testing:
Did you run the bots? yes
Did you update relevant documentation in the docs directory? yes
Did you add comments such that the purpose of the code is understandable? yes
Is there a unit test that could be added for this feature/bug? no