Skip to content

[TASK-10687] feat: redirect / to peanut.me#820

Merged
Hugo0 merged 1 commit intomainfrom
feat/redirect-to-dotme
Apr 28, 2025
Merged

[TASK-10687] feat: redirect / to peanut.me#820
Hugo0 merged 1 commit intomainfrom
feat/redirect-to-dotme

Conversation

@jjramirezn
Copy link
Copy Markdown
Contributor

@jjramirezn jjramirezn commented Apr 28, 2025

Summary by CodeRabbit

  • New Features
    • Requests to the root path ('/') are now permanently redirected to an external website (https://peanut.me).

@vercel
Copy link
Copy Markdown

vercel bot commented Apr 28, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
peanut-ui ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 28, 2025 2:59pm

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Apr 28, 2025

Walkthrough

A new permanent redirect rule has been added to the Next.js configuration. This rule instructs the application to redirect all requests from the root path '/' to the external URL 'https://peanut.me'. The redirect is set as permanent and does not utilize the base path. No other changes were made to the configuration or other parts of the codebase.

Changes

File(s) Change Summary
next.config.js Added a permanent redirect from '/' to 'https://peanut.me' with basePath: false.

Possibly related PRs

  • dev sync #477: Modifies the redirects array in next.config.js, specifically addressing root path and routing rules, closely related to the current redirect update.

Poem

The root now hops to peanut.me,
A redirect set for all to see.
With a whisk of code, the path is clear,
No more confusion, just hop over here!
🥜➡️🌐

— A happy redirecting rabbit

✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@jjramirezn jjramirezn changed the title feat: redirect / to peanut.me [TASK-10687] feat: redirect / to peanut.me Apr 28, 2025
@notion-workspace
Copy link
Copy Markdown

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
next.config.js (1)

39-44: The redirect implementation looks good, but consider the redirect chain impact.

The implementation of redirecting the root path '/' to 'https://peanut.me' is correctly configured with the appropriate parameters. Setting permanent: true means browsers will cache this redirect, which is suitable for a long-term change.

However, I noticed that there's an existing redirect from '/pioneers' to '/' (lines 70-74). With this new redirect, users accessing '/pioneers' will experience a redirect chain:

  1. '/pioneers' → '/'
  2. '/' → 'https://peanut.me'

This creates an unnecessary extra hop that impacts user experience and SEO.

Consider updating the '/pioneers' redirect to point directly to 'https://peanut.me':

{
    source: '/pioneers',
-   destination: '/',
+   destination: 'https://peanut.me',
    permanent: true,
}
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3724eec and 9d18262.

📒 Files selected for processing (1)
  • next.config.js (1 hunks)

permanent: false,
basePath: false,
},
{
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jjramirezn qn, what about other routes? if user directly goes to peanut.to/cashout, request, send or any other route? This can be a case for users coming through old social media posts?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that's fine for now @kushagrasarathe

Copy link
Copy Markdown
Contributor

@Hugo0 Hugo0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

simple, good

@Hugo0 Hugo0 merged commit 24b5185 into main Apr 28, 2025
4 checks passed
@Hugo0 Hugo0 deleted the feat/redirect-to-dotme branch July 3, 2025 18:24
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.

3 participants