Repository navigation
EPMRPP-116320 || Pages have a meta refresh tag - #1181
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
💤 Files with no reviewable changes (1)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. WalkthroughThe Docusaurus configuration no longer imports ChangesRedirect configuration
Priority: ➖ Normal Estimated code review effort: 2 (Simple) | ~10 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to The change removes client-side meta-refresh redirects in favor of the reported website-owned 301 redirects. No concrete merge-blocking defect was established, although replacement coverage could not be verified here. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 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. A rabbit hops past links of old, Comment |
Description
Removes @docusaurus/plugin-client-redirects and the releaseRedirects import from docusaurus.config.js.
The plugin generated static pages with , which the SEO crawler flags (Crawlability). Docusaurus cannot send real HTTP redirects, so the legacy URL redirects (old page names, /category/*, release URLs) are now served as 301s by the website repo (src/redirects.json, applied to Amplify).
Summary by CodeRabbit