Update _redirects

[cpengilly]

few small changes

[netlify]

✅ Deploy Preview for docs-optimism ready!

Name	Link
🔨 Latest commit	c1f9b88
🔍 Latest deploy log	https://app.netlify.com/sites/docs-optimism/deploys/67ac7b0c40a227000840b370
😎 Deploy Preview	https://deploy-preview-1355--docs-optimism.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

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

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request updates the URL redirect configuration in the public/_redirects file. The changes reorganize the structure by moving paths previously under /builders to the new /app-developers paths, and shifting routes from /chain to /superchain. Specific updates include redirecting /builders/tools/* to /app-developers/tools/:splat, modifying documentation tutorial paths, and updating chain-related resources such as /tokenlist and /addresses. Additionally, the optimist-profile redirect has been updated to point to an external community page. The catch-all rules have been expanded to cover any leftover paths in the old directories, ensuring that all outdated paths now direct users to the correct updated locations.

Possibly related PRs

• remove profile page + fix internal links #685: Updates redirect paths for optimist-profile within the _redirects file.
• update links #1337: Involves restructuring URL paths from /builders to /app-developers.
• Fix identity redirect links #1254: Addresses changes to identity documentation redirects and related URL restructuring.

Suggested labels

do-not-merge

Suggested reviewers

• sbvegan
• krofax

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e3b3f06 and c1f9b88.

📒 Files selected for processing (1)

• public/_redirects (3 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (4)

• GitHub Check: Redirect rules - docs-optimism
• GitHub Check: Header rules - docs-optimism
• GitHub Check: Pages changed - docs-optimism
• GitHub Check: pr-workflow

🔇 Additional comments (3)

public/_redirects (3)

105-106: LGTM! Consistent path updates for chain resources.

The redirects for tokenlist and addresses are properly aligned with their /chain prefixed counterparts (lines 108-109), ensuring a consistent migration to the /superchain path structure.

---

116-117: Verify the external community URL is accessible.

Both direct and /chain prefixed paths for optimist profile now redirect to an external community page.

Let's verify the URL is accessible:

✅ Verification successful

🏁 Script executed:

#!/bin/bash
# Description: Check if the community URL is accessible
curl -I https://community.optimism.io/identity/overview

Length of output: 1036

---

External URL Accessibility Confirmed

The external community URL successfully returned an HTTP 200 response with valid headers, confirming its accessibility.

---

138-140: Verify catch-all rules don't shadow specific redirects.

The catch-all rules are correctly placed at the bottom to handle any remaining paths. However, we should verify they don't accidentally override any specific redirects.

Let's check for potential conflicts:

✅ Verification successful

🏁 Script executed:

#!/bin/bash
# Description: Find any specific rules that might be shadowed by catch-alls
echo "Checking for potential conflicts with /builders/* catch-all..."
rg "^/builders/[^\s]+" | grep -v "/app-developers"

echo "Checking for potential conflicts with /chain/* catch-all..."
rg "^/chain/[^\s]+" | grep -v "/superchain"

Length of output: 3327

---

Catch-all rules are correctly ordered and do not shadow any specific redirects.

The search confirms that specific rules (e.g., those for /builders/chain-operators, /builders/node-operators, and the various /chain/* redirects) are defined with unique destinations and appear before the catch-all rules. Hence, any request matching a specific rule will be handled appropriately rather than falling through to the catch-all.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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. (Beta)
• @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.

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.