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

fix: update docusaurus redirects for new documentation structure #163

Merged
merged 5 commits into from
Dec 6, 2024

Conversation

tyaga001
Copy link
Collaborator

@tyaga001 tyaga001 commented Dec 5, 2024

  • Add redirect from /get-started to /getting-started/quickstart
  • Fix /configure-coderabbit to redirect to /getting-started/configure-coderabbit
  • Update redirects for integration and platform paths
  • Ensure all legacy paths correctly map to new documentation structure

Resolves 404 issues with old documentation links

- Add redirect from /get-started to /getting-started/quickstart
- Fix /configure-coderabbit to redirect to /getting-started/configure-coderabbit
- Update redirects for integration and platform paths
- Ensure all legacy paths correctly map to new documentation structure

Resolves 404 issues with old documentation links
@tyaga001 tyaga001 requested a review from a team as a code owner December 5, 2024 15:45
Copy link
Contributor

coderabbitai bot commented Dec 5, 2024

Walkthrough

The changes involve modifications to the Docusaurus configuration file, specifically in the plugins section. The redirect for the path /get-started has been updated to point to a new target, and a new redirect entry has been added to consolidate multiple paths leading to the same destination. The overall structure of the configuration file remains unchanged, with no modifications to other sections or public entities.

Changes

File Change Summary
docusaurus.config.ts Updated redirect from /get-started to /getting-started/quickstart/. Added new redirect for multiple paths (/configure-coderabbit, /configure-coderabbit/, /guides/configure-coderabbit, /guides/configure-coderabbit/) to /getting-started/configure-coderabbit.

Poem

In the land of code where rabbits play,
Redirects hop in a joyful ballet.
From /get-started to quickstart we go,
Paths intertwine, like a stream's gentle flow.
With each little change, our guide's now bright,
Hooray for the tweaks that bring us delight! 🐇✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 8549987 and 34dd0da.

📒 Files selected for processing (1)
  • docusaurus.config.ts (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • docusaurus.config.ts

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

Copy link

cloudflare-workers-and-pages bot commented Dec 5, 2024

Deploying coderabbit-docs with  Cloudflare Pages  Cloudflare Pages

Latest commit: 108ebe0
Status: ✅  Deploy successful!
Preview URL: https://5878e525.coderabbit-docs.pages.dev
Branch Preview URL: https://fix-doc-redirects.coderabbit-docs.pages.dev

View logs

@tyaga001
Copy link
Collaborator Author

tyaga001 commented Dec 5, 2024

@aravindputrevu @coderabbitai I tested all the redirects. Below is the testing summary.

Redirect Testing Summary

All redirects were tested in production build using npm run build && npm run serve.
Each path was verified to redirect to its correct destination.

✅ Getting Started Section

  • /get-started/getting-started/quickstart
  • /configure-coderabbit/getting-started/configure-coderabbit

✅ Guides Section

  • /guides/customize-coderabbit/getting-started/configure-coderabbit
  • /guides/prompt-customization/guides/review-instructions
  • /guides/configure-coderabbit/getting-started/configure-coderabbit

✅ Integration to Platform Migrations

  • /integrations/saas-gitlab/platforms/gitlab-com
  • /integrations/self-hosted-gitlab/platforms/self-hosted-gitlab
  • /integrations/self-hosted-github/platforms/github-enterprise-server

✅ Platform Path Updates

  • /platforms/saas-azure-devops/platforms/azure-devops
  • /platforms/saas-gitlab/platforms/gitlab-com
  • /platforms/self-hosted-github/platforms/github-enterprise-server

Additional verification:

  • Tested both with and without trailing slashes
  • Verified content loads correctly at destination
  • Checked in incognito mode to avoid caching issues

Copy link
Contributor

coderabbitai bot commented Dec 5, 2024

Tip

For best results, initiate chat on the files or code changes.

@tyaga001 Thank you for thoroughly testing all the redirects and providing the comprehensive summary. It's great to hear that all redirects are functioning correctly and that the 404 issues have been resolved. If there's anything else I can assist with, please let me know.

Copy link
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: 1

🧹 Outside diff range and nitpick comments (1)
docusaurus.config.ts (1)

Based on the search results, I can generate the final response as I've found evidence of potential missing redirects and inconsistencies.

Several documentation paths need additional redirects

The search results revealed some paths that are currently being referenced but may not be properly covered by the redirect rules:

  • /integrations/knowledge-base is referenced in docs but missing from redirects
  • /about/support is referenced but not covered in redirects
  • /img/integrations/logo.svg is referenced in multiple places but may need a redirect if the image structure changed
  • /integrations/knowledge-base#self-hosted is referenced but the base path isn't covered by redirects

The current redirect changes are good but need to be expanded to include these additional paths to prevent potential 404s.

🔗 Analysis chain

Line range hint 44-91: Verify coverage of all legacy documentation paths

To ensure we've addressed all potential 404 errors, let's verify if there are any frequently accessed legacy paths that still need redirects.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check access logs and documentation references for potential missing redirects

# Search for markdown files that might reference old paths
rg -g "*.md" -g "*.mdx" "/get-started|/configure|/guides" 

# Search for potential internal links that might need redirects
rg -g "*.md" -g "*.mdx" "\[.*\]\(/[^)]+\)"

Length of output: 9344

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between e35ab81 and cea5350.

📒 Files selected for processing (1)
  • docusaurus.config.ts (2 hunks)
🔇 Additional comments (1)
docusaurus.config.ts (1)

44-45: LGTM: Redirect path update is correct and consistent

The redirect from "/get-started/" to "/getting-started/quickstart/" is properly configured and maintains consistent trailing slashes.

docusaurus.config.ts Outdated Show resolved Hide resolved
- Add redirect from /get-started to /getting-started/quickstart
- Fix /configure-coderabbit to redirect to /getting-started/configure-coderabbit
- Update redirects for integration and platform paths
- Ensure all legacy paths correctly map to new documentation structure

Resolves 404 issues with old documentation links
[dependabot skip]
@tyaga001 tyaga001 merged commit 106208c into main Dec 6, 2024
4 checks passed
@tyaga001 tyaga001 deleted the fix/doc-redirects branch December 6, 2024 12:13
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.

4 participants