Copy resources into output directory instead of moving them. #363
Conversation
There was a problem hiding this comment.
Summary of Changes
Hello @annajowang, 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!
I've made a crucial change to how resources are handled during the build process for Next.js applications. Previously, resources were moved from their original location to the output directory, which could lead to issues if those resources were still required elsewhere. Now, I've updated the process to copy these resources instead, ensuring that the originals remain intact while a duplicate is placed in the output. This change improves the robustness and reliability of the resource handling, preventing unintended side effects of destructive file operations.
Highlights
- Changed resource transfer from move to copy: I've updated the resource handling logic to use
copyinstead ofmovewhen transferring files to the output directory. This ensures that the original resources remain in their source location, preventing potential issues where they might be needed later in the build or deployment process. - Imported
copyfunction fromfs-extra: To facilitate the change from moving to copying resources, I've added thecopyfunction to thefs-extraimport insrc/utils.ts, making it available for use within the module.
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. ↩
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
This is part one of making our adapter builds idempotent.