Skip to content

Update README.md - #5008

Closed
AIPDD-work wants to merge 1 commit into
QuantumNous:mainfrom
AIPDD-work:patch-3
Closed

Update README.md#5008
AIPDD-work wants to merge 1 commit into
QuantumNous:mainfrom
AIPDD-work:patch-3

Conversation

@AIPDD-work

@AIPDD-work AIPDD-work commented May 21, 2026

Copy link
Copy Markdown

⚠️ 提交说明 / PR Notice

Important

  • 请提供人工撰写的简洁摘要,避免直接粘贴未经整理的 AI 输出。

📝 变更描述 / Description

(简述:做了什么?为什么这样改能生效?请基于你对代码逻辑的理解来写,避免粘贴未经整理的内容)

🚀 变更类型 / Type of change

  • 🐛 Bug 修复 (Bug fix) - 请关联对应 Issue,避免将设计取舍、理解偏差或预期不一致直接归类为 bug
  • ✨ 新功能 (New feature) - 重大特性建议先通过 Issue 沟通
  • ⚡ 性能优化 / 重构 (Refactor)
  • 📝 文档更新 (Documentation)

🔗 关联任务 / Related Issue

  • Closes # (如有)

✅ 提交前检查项 / Checklist

  • 人工确认: 我已亲自整理并撰写此描述,没有直接粘贴未经处理的 AI 输出。
  • 非重复提交: 我已搜索现有的 IssuesPRs,确认不是重复提交。
  • Bug fix 说明: 若此 PR 标记为 Bug fix,我已提交或关联对应 Issue,且不会将设计取舍、预期不一致或理解偏差直接归类为 bug。
  • 变更理解: 我已理解这些更改的工作原理及可能影响。
  • 范围聚焦: 本 PR 未包含任何与当前任务无关的代码改动。
  • 本地验证: 已在本地运行并通过测试或手动验证,维护者可以据此复核结果。
  • 安全合规: 代码中无敏感凭据,且符合项目代码规范。

📸 运行证明 / Proof of Work

(请在此粘贴截图、关键日志或测试报告,以证明变更生效)

Summary by CodeRabbit

  • Documentation
    • README completely redesigned with full Chinese localization. Restructured and updated all major sections including installation procedures, quick start guide, deployment methods, key features documentation, and comprehensive model support information. Added Docker and volume configuration guidance. Enhanced multi-machine deployment instructions and guidelines. Revised branding, license details, and repository references.

Review Change Stack

@coderabbitai

coderabbitai Bot commented May 21, 2026

Copy link
Copy Markdown
Contributor

Walkthrough

README.md is comprehensively rewritten to localize the project documentation from English to Chinese and rebrand it as AIPDD-new-api. The title, navigation, installation guidance, feature descriptions, deployment instructions, and footer are all translated and updated to reflect the new project branding.

Changes

README Chinese Localization and Rebranding

Layer / File(s) Summary
Title and project branding rewrite
README.md
README title and initial branding are replaced with new Chinese "AIPDD-new-api" heading.
Installation and quick start sections
README.md
Navigation, project description, and installation/quick start content converted to Chinese with updated Docker instructions and feature documentation through deployment guidance sections.
Configuration, deployment, and footer branding
README.md
MySQL configuration label, deployment guidance, path documentation, and 宝塔面板 installation section updated to Chinese; footer, license, and related projects sections rewritten with AIPDD-new-api branding.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

  • QuantumNous/new-api#1627: Both PRs modify project README.md documentation, including branding/structure updates and environment variable configuration changes.
  • QuantumNous/new-api#2486: Both PRs modify README documentation—this PR rewrites Chinese README content and headings, while the related PR updates README documentation link targets in routing.

Poem

🐰 A README dressed in Hanzi bright,
Rebranded swift as morning light,
AIPDD now leads the way,
With Docker steps and guides to play,
The rabbit cheers—localization day! 🌟

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'Update README.md' is vague and generic, failing to convey the significant nature of the changes—a comprehensive rewrite translating the README from English to Chinese and updating the entire documentation structure. Consider a more descriptive title such as 'Translate README.md to Chinese and update AIPDD documentation' to better reflect the scope and nature of the substantial changes.
✅ Passed checks (4 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@README.md`:
- Around line 159-160: Update the inconsistent documentation domains by
replacing any occurrences of "doc.newapi.pro" with "docs.newapi.pro" in the
README entries that reference Google Gemini and the Rerank 模型 (the URLs
"https://doc.newapi.pro/api/google-gemini-chat" and
"https://docs.newapi.pro/zh/docs/api/ai-model/rerank/create-rerank" and the
other instances noted around the same section); ensure the bullet lines
containing "Google Gemini" and "Rerank 模型" (and the other two occurrences called
out) use the canonical "https://docs.newapi.pro" host so links across the README
remain consistent.
- Around line 62-63: The README shows inconsistent repo names: the git clone
uses "aipdd-new-api" while the subsequent cd uses "new-api", causing copy/paste
failures; update the commands so they reference the same directory name in both
places (either change the clone URL to end with "new-api" or change the cd
commands to "cd aipdd-new-api") and make the same fix for the duplicate
occurrence later in the file (the second block around lines 285–287) so both
clone and cd consistently point to the identical repository directory.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: d170a132-cdf7-4494-b1ed-25c8b30b0b16

📥 Commits

Reviewing files that changed from the base of the PR and between 006e801 and 14a1fed.

📒 Files selected for processing (1)
  • README.md

Comment thread README.md
Comment on lines +62 to 63
git clone https://github.com/liujh0729-jpg/aipdd-new-api.git
cd new-api

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Unify repository clone path and cd command to avoid setup failure (Line 62, Line 63, Line 285, Line 286).

The two install paths point to different repos, and one section clones aipdd-new-api but then enters new-api. This can break copy-paste onboarding.

Suggested doc fix
- git clone https://github.com/liujh0729-jpg/aipdd-new-api.git
- cd new-api
+ git clone https://github.com/liujh0729-jpg/aipdd-new-api.git
+ cd aipdd-new-api
- git clone https://github.com/QuantumNous/new-api.git
- cd new-api
+ git clone https://github.com/liujh0729-jpg/aipdd-new-api.git
+ cd aipdd-new-api

Also applies to: 285-287

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@README.md` around lines 62 - 63, The README shows inconsistent repo names:
the git clone uses "aipdd-new-api" while the subsequent cd uses "new-api",
causing copy/paste failures; update the commands so they reference the same
directory name in both places (either change the clone URL to end with "new-api"
or change the cd commands to "cd aipdd-new-api") and make the same fix for the
duplicate occurrence later in the file (the second block around lines 285–287)
so both clone and cd consistently point to the identical repository directory.

Comment thread README.md
Comment on lines +159 to +160
- ⚡ [Google Gemini](https://doc.newapi.pro/api/google-gemini-chat)
- 🔄 [Rerank 模型](https://docs.newapi.pro/zh/docs/api/ai-model/rerank/create-rerank)CohereJina

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Normalize documentation domains to prevent stale/broken links (Line 159, Line 209, Line 210).

These entries use doc.newapi.pro while the rest of the README consistently uses docs.newapi.pro.

Suggested doc fix
- - ⚡ [Google Gemini](https://doc.newapi.pro/api/google-gemini-chat)
+ - ⚡ [Google Gemini](https://docs.newapi.pro/zh/docs/api/ai-model/chat/gemini/geminirelayv1beta)

- | 🎨 Midjourney-Proxy | [Midjourney-Proxy(Plus)](https://github.com/novicezk/midjourney-proxy) | [文档](https://doc.newapi.pro/api/midjourney-proxy-image) |
+ | 🎨 Midjourney-Proxy | [Midjourney-Proxy(Plus)](https://github.com/novicezk/midjourney-proxy) | [文档](https://docs.newapi.pro/zh/docs/api/ai-model/images/midjourney/) |

- | 🎵 Suno-API | [Suno API](https://github.com/Suno-API/Suno-API) | [文档](https://doc.newapi.pro/api/suno-music) |
+ | 🎵 Suno-API | [Suno API](https://github.com/Suno-API/Suno-API) | [文档](https://docs.newapi.pro/zh/docs/api/) |

Also applies to: 209-210

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@README.md` around lines 159 - 160, Update the inconsistent documentation
domains by replacing any occurrences of "doc.newapi.pro" with "docs.newapi.pro"
in the README entries that reference Google Gemini and the Rerank 模型 (the URLs
"https://doc.newapi.pro/api/google-gemini-chat" and
"https://docs.newapi.pro/zh/docs/api/ai-model/rerank/create-rerank" and the
other instances noted around the same section); ensure the bullet lines
containing "Google Gemini" and "Rerank 模型" (and the other two occurrences called
out) use the canonical "https://docs.newapi.pro" host so links across the README
remain consistent.

@seefs001 seefs001 closed this May 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants