-
Notifications
You must be signed in to change notification settings - Fork 23
Bump kayobe-automation #1885
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
base: stackhpc/2025.1
Are you sure you want to change the base?
Bump kayobe-automation #1885
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 @m-bull, 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 updates the kayobe-automation
subproject to resolve an issue where kayobe
commands were not properly utilizing the directory specified by KAYOBE_CONFIG_PATH
. The change ensures that kayobe
operations are executed from the intended configuration path, improving reliability and consistency.
Highlights
- kayobe-automation Subproject Update: The
kayobe-automation
subproject has been updated to a newer commit (dc8baaf
from68a34ce
). This update incorporates a fix that ensureskayobe
commands are correctly executed from the directory specified by theKAYOBE_CONFIG_PATH
environment variable. - Release Note Addition: A new release note has been added to document the
kayobe-automation
bump, specifically highlighting the fix forkayobe
commands respecting theKAYOBE_CONFIG_PATH
.
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
-
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
This pull request updates the kayobe-automation
submodule to incorporate a fix ensuring kayobe commands execute from the directory specified by KAYOBE_CONFIG_PATH
. A corresponding release note is also added. My review includes a suggestion to improve the clarity and formatting of this new release note by making it more concise and properly formatting the environment variable as code.
releasenotes/notes/kayobe-automation-change-directory-dddf4772b3ee81af.yaml
Outdated
Show resolved
Hide resolved
475281d
to
8f84f4f
Compare
300a2a8
to
a7d0e74
Compare
Bump kayobe-automation to include fix that runs kayobe commands from the directory specified in KAYOBE_CONFIG_PATH [1]. [1] stackhpc/kayobe-automation#78
Make diagnostics_path_local in the home directory of the stack user to ensure that outputs can be copied back to the host correctly. This approach mirrors the one taken by the stackhpc-cloud-tests custom playbook.
a7d0e74
to
f85a9c5
Compare
Bump kayobe-automation to include fix that runs kayobe commands from the directory specified in
KAYOBE_CONFIG_PATH [1].
[1] stackhpc/kayobe-automation#78