Repository navigation
Move to debateowl.com and 301 debate.pi-stack.org - #246
Merged
Merged
Conversation
|
Caution Review failedThe pull request is closed.
Note 🎁 Summarized by CodeRabbit Free
Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Moves DebateOwl to https://debateowl.com and retires debate.pi-stack.org.
Changes
src/config/site.jsonorigin is nowhttps://debateowl.com, and the brand isDebateOwl(titles no longer end "| DebateOwl by Pi-Stack"). The SEO pages and llms.txt were regenerated withscripts/generate_seo_content.py. index.html og/twitter/author, humans.txt, robots.txt sitemap, embed canonical, README, AGENTS, docs, e2e/tests andplaywright.production.config.tsare updated too. Footer copyright now reads "© 2026 Pi-Stack.", and the JSON-LD organization stays Pi-Stack.vercel.jsonredirect sends every path ondebate.pi-stack.orgtohttps://debateowl.com/:pathwith a 301, and Vercel appends the query./sw.jsis the only exception.check-site.mjsignores host-scoped rules.debate.pi-stack.orgthe newsw.jsskips precaching, clears every cache, unregisters, and reloads its tabs. The tabs then follow the 301. Fetch and message handlers do nothing there. Tested with Playwright: today's prod worker is installed on the old host, then the host is flipped to the new behaviour. Deep links land on debateowl.com with the query intact, and the old origin ends up with 0 registrations and 0 caches._shared/cors.ts), checkout callbacks and workspace-invites now allowhttps://debateowl.com, and it is the fallback origin.https://debate.pi-stack.orgstays allowed.Left on purpose
scripts/gsc_submit.py, which is tied to the Search Console properties.debatelab-*URL slugs.Before merging
The prod edge functions must be redeployed with the new CORS first. Today they answer
Origin: https://debateowl.comwithAccess-Control-Allow-Origin: https://debate.pi-stack.org, so once the 301 is live every AI, checkout and announcement call from debateowl.com fails.npm run verifypasses locally.