-
Notifications
You must be signed in to change notification settings - Fork 2k
fix: Update repository URL #4143
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
The previous repo is deprecated. All of its content and history has been moved to google-cloud-node.
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 @faube, 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 repository metadata within the package.json
for the reCAPTCHA Enterprise demo application. The primary purpose is to correctly point to the new location of the reCAPTCHA Enterprise content, which has been migrated from a standalone repository to the google-cloud-node
monorepository. This ensures that the project's source control information is accurate and up-to-date.
Highlights
- Repository URL Update: The
repository.url
inrecaptcha_enterprise/demosite/app/package.json
has been updated fromhttps://github.com/googleapis/nodejs-recaptcha-enterprise.git
tohttps://github.com/googleapis/google-cloud-node.git
. This change reflects the migration of the reCAPTCHA Enterprise content to a new monorepository. - Monorepo Directory Specification: A new
repository.directory
field, set topackages/google-cloud-recaptchaenterprise
, has been added to thepackage.json
. This explicitly defines the sub-directory for the reCAPTCHA Enterprise package within the newgoogle-cloud-node
monorepository structure.
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 or fill out our survey 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.
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 updates the repository URL to point to the new google-cloud-node
monorepo. My review identifies a likely typo in the directory
path within package.json
. Correcting this will ensure that repository links and related npm tooling function correctly.
@@ -12,7 +12,8 @@ | |||
}, | |||
"repository": { | |||
"type": "git", | |||
"url": "https://github.com/googleapis/nodejs-recaptcha-enterprise.git" | |||
"directory": "packages/google-cloud-recaptchaenterprise", |
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.
The directory path for the package within the monorepo appears to be incorrect. For a package named @google-cloud/recaptcha-enterprise
, the directory in the google-cloud-node
monorepo is expected to be packages/recaptcha-enterprise
.
The current value packages/google-cloud-recaptchaenterprise
seems to have a redundant google-cloud-
prefix. An incorrect path here will break repository links on npmjs.com and for tools like npm repo
.
"directory": "packages/recaptcha-enterprise",
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.
@faube can you verify if this warning is valid?
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.
It seems like this is gemini hallucinating.
according to this page
https://docs.npmjs.com/cli/v11/configuring-npm/package-json#repository
"If the package.json for your package is not in the root directory (for example if it is part of a monorepo), you can specify the directory in which it lives:"
Since the full URL is
https://github.com/googleapis/google-cloud-node/tree/main/packages/google-cloud-recaptchaenterprise
the directory under the root directory is packages/google-cloud-recaptchaenterprise
In any case this has no runtime impact, it's essentially documentation.
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.
LGTM
The previous repo is deprecated. All of its content and history has been moved to google-cloud-node.