[codex] replace stale shifu.run website links - #392
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: abe0c9ebab
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| <img src="/blog-220930/shifu-install.png" width="60%" /> | ||
|
|
||
| You can also check out [a more detailed tutorial on installing Shifu locally](https://shifu.run/docs/guides/install-shifu-dev). | ||
| You can also check out [a more detailed tutorial on installing Shifu locally](https://shifu.dev/docs/guides/install-shifu-dev). |
There was a problem hiding this comment.
This replacement still points readers to https://shifu.dev/docs/guides/install-shifu-dev, but the local-install doc in this Docusaurus repo is docs/guides/install/install-shifu-dev.md, which publishes under /docs/guides/install/install-shifu-dev/ (the same stale path also appears in the other changed local-install blog links). As written, the cleanup swaps the dead domain for a still-broken page, so users following the updated tutorial link hit a 404 instead of the current local install guide.
Useful? React with 👍 / 👎.
1 participant
What type of PR is this?
/kind cleanup
/kind documentation
What this PR does / why we need it:
Replaces stale public
shifu.runlinks with currentshifu.devlinks across docs, blog content, demo navigation, Chinese translations, and Docusaurus edit links. It also removes a dead commentedcloud.shifu.rundemo block from source.shifu.runno longer resolves, while the correspondingshifu.devpages and demo disclaimer page are live. This keeps users on working documentation and demo paths.Which issue(s) this PR fixes:
N/A
How is this PR tested:
bun run buildSpecial notes for your reviewer:
This PR intentionally leaves
azure-pipelines/deploy.ymldeployment-internal names alone. The endpoint and/var/www/shifu.runpath may be legacy deployment plumbing for the current site host, so changing them should be handled separately with server-side deploy verification.Does this PR introduce a user-facing change?
Yes, stale website links now point at
shifu.devinstead of the non-resolvingshifu.rundomain.Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: