Add /will and /khaliq vanity aliases for the meet links#26
Conversation
/will redirects to the same destination as /meet-with-will, and /khaliq to the same destination as /meet-with-khaliq. Also fix the redirect test to expect query params carried through to the destination, matching the worker's intentional utm-forwarding behavior. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TfQs9DMir9AvWUP1mL6ZJd
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
Warning Review limit reached
Next review available in: 50 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe router adds ChangesVanity redirect aliases
Estimated code review effort: 2 (Simple) | ~5 minutes Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
|
Preview deployed!
This is a Cloudflare Workers preview version of this PR's build. |
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TfQs9DMir9AvWUP1mL6ZJd
Summary
agentrelay.com/willnow redirects to the same Google Calendar booking link as/meet-with-willagentrelay.com/khaliqnow redirects to the same Calendly link as/meet-with-khaliqTest fix
The existing vanity-redirect tests were failing on the base branch: they asserted the
Locationheader equals the bare destination, but the worker intentionally carries request query params (e.g.utm_source) through to the redirect. Updated the assertion to expect the forwarded query string — all 72 router tests now pass.🤖 Generated with Claude Code
https://claude.ai/code/session_01TfQs9DMir9AvWUP1mL6ZJd
Generated by Claude Code
Summary by cubic
Added vanity aliases for meeting links:
/willand/khaliqnow redirect to the same destinations as/meet-with-willand/meet-with-khaliq. Updated tests to expect forwarded query params and noted the aliases in the router docs.New Features
agentrelay.com/will-> same Google Calendar link as/meet-with-will.agentrelay.com/khaliq-> same Calendly link as/meet-with-khaliq.Refactors
WILL_CALENDAR_URL,KHALIQ_CALENDAR_URL, andVIRTUAL_OFFICE_URLconstants and reused them in the router and tests.Written for commit 95a984b. Summary will update on new commits.