docs: correct documentation URL from astrbot.app to docs.astrbot.app#7610
docs: correct documentation URL from astrbot.app to docs.astrbot.app#7610Hongbro886 wants to merge 1 commit intoAstrBotDevs:masterfrom
Conversation
There was a problem hiding this comment.
Code Review
This pull request updates the Docker deployment documentation URL from astrbot.app to docs.astrbot.app across multiple language versions of the README. Feedback suggests extending this update to other documentation links within the same files to maintain consistency and ensure all links point to the correct subdomain.
| For users familiar with containers and looking for a more stable, production-ready deployment method, we recommend deploying AstrBot with Docker / Docker Compose. | ||
|
|
||
| Please refer to the official documentation: [Deploy AstrBot with Docker](https://astrbot.app/deploy/astrbot/docker.html#%E4%BD%BF%E7%94%A8-docker-%E9%83%A8%E7%BD%B2-astrbot). | ||
| Please refer to the official documentation: [Deploy AstrBot with Docker](https://docs.astrbot.app/deploy/astrbot/docker.html#%E4%BD%BF%E7%94%A8-docker-%E9%83%A8%E7%BD%B2-astrbot). |
There was a problem hiding this comment.
The pull request title indicates a correction of the documentation URL from astrbot.app to docs.astrbot.app, but this update has only been applied to the Docker deployment link. Several other documentation links in this file (and other README files) still point to the old domain (e.g., the main Documentation link at line 33 and the various deployment guides at line 142). For consistency and to ensure users are directed to the correct documentation site, please consider updating all relevant documentation links to use the docs.astrbot.app subdomain.
fix #7479
Modifications / 改动点
修改所有README中Docker部署的链接
Checklist / 检查清单
😊 If there are new features added in the PR, I have discussed it with the authors through issues/emails, etc.
/ 如果 PR 中有新加入的功能,已经通过 Issue / 邮件等方式和作者讨论过。
👀 My changes have been well-tested, and "Verification Steps" and "Screenshots" have been provided above.
/ 我的更改经过了良好的测试,并已在上方提供了“验证步骤”和“运行截图”。
🤓 I have ensured that no new dependencies are introduced, OR if new dependencies are introduced, they have been added to the appropriate locations in
requirements.txtandpyproject.toml./ 我确保没有引入新依赖库,或者引入了新依赖库的同时将其添加到
requirements.txt和pyproject.toml文件相应位置。😮 My changes do not introduce malicious code.
/ 我的更改没有引入恶意代码。
Summary by Sourcery
Documentation: