Skip to content
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

Replace remotePatterns with domains in next.config.ts #1782

Merged
merged 1 commit into from
Mar 18, 2025

Conversation

imbhargav5
Copy link
Owner

@imbhargav5 imbhargav5 commented Mar 18, 2025


For more details, open the Copilot Workspace session.

Copy link

codesandbox bot commented Mar 18, 2025

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

Copy link

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

Hello @imbhargav5, 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 replaces the remotePatterns configuration with domains in the next.config.ts file. This change configures the allowed image domains for the Next.js application, specifically allowing images from 'avatars.githubusercontent.com'. The change simplifies the configuration by directly specifying the allowed domains instead of using a more complex pattern matching system.

Highlights

  • Configuration Change: Replaces remotePatterns with domains in next.config.ts to configure allowed image domains.
  • Image Optimization: Configures Next.js to allow images from 'avatars.githubusercontent.com'.

Changelog

  • apps/website/next.config.ts
    • Replaced remotePatterns configuration with domains to specify allowed image domains.
    • Configured allowed domain to be 'avatars.githubusercontent.com'.
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.


Trivia time!

What is the primary use case for Next.js?

Click here for the answer
Next.js is primarily used for building server-rendered React applications and static websites.

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.

@imbhargav5 imbhargav5 merged commit 89b27ce into main Mar 18, 2025
2 of 4 checks passed
Copy link

@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

The pull request replaces remotePatterns with domains in the next.config.ts file. This change appears to be related to how Next.js handles image optimization with external sources. The change itself is small, but it's important to ensure it doesn't introduce any regressions or unexpected behavior.

Merge Readiness

The code change is straightforward. Given the simplicity of the change, it appears ready to be merged. However, it's recommended to verify that the image optimization still works as expected after this change, especially in different environments (development, production). I am unable to directly approve the pull request, and other reviewers should review and approve this code before merging.

@imbhargav5 imbhargav5 deleted the update-next-config branch March 18, 2025 17:36
Copy link

netlify bot commented Mar 18, 2025

Deploy Preview for rooksjs ready!

Name Link
🔨 Latest commit 55346a9
🔍 Latest deploy log https://app.netlify.com/sites/rooksjs/deploys/67d9af2c90381200080f00f9
😎 Deploy Preview https://deploy-preview-1782--rooksjs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant