fix: update deployment paths for custom domain#77
Conversation
|
Warning Review limit reached
More reviews will be available in 50 minutes and 58 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (2)
WalkthroughThe PR migrates the project from its GitHub Pages hosting ( ChangesCustom Domain Migration
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested labels
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@index.html`:
- Line 30: The canonical URL in index.html has been updated to
https://orgexplorer.aossie.org/, but this change must be synchronized with the
crawler discovery files. Update public/sitemap.xml to replace any references to
the old /OrgExplorer/ path with the new canonical domain
https://orgexplorer.aossie.org/, and similarly update public/robots.txt to point
crawlers to the correct domain instead of the old path. This ensures search
engines index the correct URLs and maintain proper deep-link discovery after
deployment.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: 3625261d-ac8d-49a6-a1e3-753b4583ac3b
📒 Files selected for processing (3)
index.htmlsrc/main.jsxvite.config.js
Addressed Issues:
Fixes #
Screenshots/Recordings:
Additional Notes:
Root cause:
-Vite was still building assets using the old GitHub Pages path (/OrgExplorer/).
-React Router was also using basename="/OrgExplorer" in production.
After updating:
-vite.config.js: base: "/"
-BrowserRouter: removed the /OrgExplorer basename
-Updated domain-specific metadata URLs in index.html
Verification:
-npm run build completes successfully.
-npm run preview now renders the application correctly.
Checklist
We encourage contributors to use AI tools responsibly when creating Pull Requests. While AI can be a valuable aid, it is essential to ensure that your contributions meet the task requirements, build successfully, include relevant tests, and pass all linters. Submissions that do not meet these standards may be closed without warning to maintain the quality and integrity of the project. Please take the time to understand the changes you are proposing and their impact.
Summary by CodeRabbit