-
Notifications
You must be signed in to change notification settings - Fork 7
CID-3446 #623
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @natnesi, 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 primarily focuses on updating and expanding the project's documentation. It introduces new sections and release notes for the Freezer long-term storage service, adjusts the navigation order for existing Jupyter release notes, and includes a minor configuration change to a module's availability count.
Highlights
- Documentation Structure Updates: Modified existing and added new navigation configuration files (
.pages.yml
) to organize documentation, specifically reordering entries for Jupyter release notes and integrating a new section for Freezer long-term storage. - New Release Notes Content: Introduced a new release notes document for
freezer.nesi.org.nz
, detailing updates related to improved email handling, resilient provisioning, and validation. - Module Configuration Adjustment: Updated the
total
count for thecomsol@uc
module inmodule-list.json
from 5 to 0, likely indicating a change in its availability or allocation.
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 is currently in preview and 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 to provide feedback.
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.
Docs updated, clear and bright, Navigation set just right, Code changes, a small tweak, For users, a new peak, Information, shining light.
Footnotes
-
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. ↩
Test deployment available at https://callumwalley.github.io/mkdocs-demo-deploy/nesi/support-docs/CID-3446 See all deployed demo sites |
a couple minor typo fixes Signed-off-by: Jana Makar <[email protected]>
tweaks to release notes Signed-off-by: Claire Rye <[email protected]>
first draft, please Claire and Jana review.