-
Notifications
You must be signed in to change notification settings - Fork 6
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
Update index.md #457
base: main
Are you sure you want to change the base?
Update index.md #457
Conversation
Removed a couple of known issues that we have resolved Signed-off-by: junhuhnesi <[email protected]>
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.
Hello @junhuhnesi, 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!
Summary of Changes
This pull request updates the index.md
file in the docs/Scientific_Computing/Interactive_computing_with_NeSI_OnDemand/known_issues/
directory. The purpose is to remove resolved known issues from the list of known issues for NeSI OnDemand. Specifically, the 'Token expiry' and 'User accounts with dots in the username' issues have been removed.
Highlights
- Known Issues Update: Removes resolved issues ('Token expiry' and 'User accounts with dots in the username') from the known issues list in the NeSI OnDemand documentation.
- Documentation Maintenance: Keeps the known issues documentation up-to-date by removing entries that are no longer relevant.
Changelog
- docs/Scientific_Computing/Interactive_computing_with_NeSI_OnDemand/known_issues/index.md
- Removed the 'Token expiry' known issue.
- Removed the 'User accounts with dots in the username' known issue.
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.
A bug is squashed,
The code now runs so clean,
A joyful release.
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. ↩
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.
Code Review
The pull request removes entries from the known issues page for NeSI OnDemand. This is a positive step as it keeps the documentation up-to-date and accurate for users. The changes are straightforward and address the stated goal of removing resolved issues.
Merge Readiness
The pull request appears ready to be merged, as it removes outdated information from the documentation. I am unable to directly approve the pull request, and recommend that others review and approve this code before merging.
Removed a couple of known issues that we have resolved