Skip to content

Conversation

@shrutip90
Copy link
Contributor

Checklist (if applicable):

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @shrutip90, 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 introduces a fix to standardize the pathing for dynamic actions by consistently prepending a forward slash to their prefixes. This change aims to improve the reliability and predictability of dynamic action resolution within the system, ensuring that all dynamic action paths adhere to a uniform format.

Highlights

  • Dynamic Action Path Standardization: A leading slash has been added to the dapPrefix for dynamic actions, ensuring consistent path formatting.
  • Test Alignment: Unit tests have been updated to reflect the new slash-prefixed dynamic action paths, confirming the correctness of the change.

🧠 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.

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.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a 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 correctly fixes a bug in how dynamic action keys are constructed by adding a leading slash to the prefix. This ensures that the generated keys for dynamic actions are consistent with the absolute path format used throughout the registry, which is essential for them to be looked up and resolved correctly. The tests have been properly updated to validate the fix. The change is concise, correct, and improves the robustness of dynamic action handling.

@shrutip90 shrutip90 enabled auto-merge (squash) December 19, 2025 15:54
@pavelgj pavelgj changed the title fix: Add slash prefix for dynamic actions Dec 19, 2025
@shrutip90 shrutip90 merged commit a4b330c into main Dec 19, 2025
5 checks passed
@shrutip90 shrutip90 deleted the sp/dyn branch December 19, 2025 15:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

2 participants