chore: standardize repository setup#287
Conversation
|
Warning Review limit reached
More reviews will be available in 27 minutes and 56 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?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 credits. 🚦 How do rate 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 see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
Walkthrough将文档构建输出切到 Changes构建、CI 与文档基础设施更新
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
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 |
❌ Deploy failed
📋 Build log (last lines)🤖 Powered by surge-preview |
|||||||||
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #287 +/- ##
==========================================
Coverage 100.00% 100.00%
==========================================
Files 15 13 -2
Lines 902 238 -664
Branches 89 50 -39
==========================================
- Hits 902 238 -664 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces several configuration and documentation updates. Key changes include adding a Vercel configuration file (vercel.json) and adjusting .dumirc.ts to support Vercel deployments, adding a GitHub funding configuration, updating the README.md with enhanced documentation and API details, and introducing new scripts (build, prettier, tsc) to package.json. Additionally, the TypeScript configuration has been updated to explicitly include source, test, and documentation directories. There are no review comments, and I have no feedback to provide.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
|
AI review follow-up:
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
Warning Review the following alerts detected in dependencies. According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
🧹 Nitpick comments (2)
README.zh-CN.md (2)
39-39: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win混合语言：请完整翻译特性描述。
第 39 行 "暴露
Colorhelpers for hex, RGB, and HSB conversions" 仍为英文，应统一为中文，例如："暴露Color辅助方法，支持 hex、RGB 和 HSB 转换"。🤖 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.zh-CN.md` at line 39, The feature description in README.zh-CN.md is still in English and should be fully translated to Chinese. Update the `Color` helpers sentence so it consistently uses Chinese wording while preserving the meaning of hex, RGB, and HSB conversions, and keep the `Color` reference recognizable in the translated text.
93-99: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick winColor 方法说明未翻译。
toHexString、toHsb、toHsbString、toRgb、toRgbString的 Description 列仍为英文，应与表头「说明」保持一致，翻译为中文。例如：
Convert to hex color string→转换为十六进制颜色字符串Convert to HSB object→转换为 HSB 对象🤖 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.zh-CN.md` around lines 93 - 99, The Color method descriptions in the README.zh-CN table are still in English and should be translated to match the “说明” column. Update the entries for toHexString, toHsb, toHsbString, toRgb, and toRgbString in the README.zh-CN.md table so their descriptions are Chinese equivalents, keeping the method names and type signatures unchanged.
🤖 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 @.github/workflows/main.yml:
- Around line 5-6: The reusable workflow reference in the main workflow is too
loosely pinned and inherits all secrets, so update the workflow call to the
specific reusable workflow identifier and pin it to an immutable commit SHA
instead of the moving main branch. Remove secrets: inherit and, if any secrets
are still required, pass only the explicit ones supported by the called
workflow’s workflow_call.secrets contract; otherwise drop secret passing
entirely.
In @.github/workflows/surge-preview.yml:
- Line 22: The conditional on the Surge preview steps is directly referencing
secrets, which GitHub Actions does not allow in an if expression. Update the
workflow by moving SURGE_TOKEN into an env mapping first, then change the
affected step conditions to check env.SURGE_TOKEN instead; use the existing
Surge-related step blocks in surge-preview.yml as the place to apply the fix.
In `@package.json`:
- Around line 31-34: The gh-pages build chain does not set GH_PAGES, so
docs:build still produces root-path assets instead of the GitHub Pages base
path. Update the publishing flow by introducing or using a GH_PAGES=1 build
script for the gh-pages command, and reference the existing docs:build,
docs:deploy, and gh-pages scripts in package.json so the GitHub Pages deployment
uses the correct base/publicPath configured by .dumirc.ts.
In `@README.zh-CN.md`:
- Line 87: The API table header translation is incorrect in the README, where
the `ColorGenInput` field name `value` is rendered as “价值”; update the table
entry to use the original parameter name `value` or a clear label like “当前值”
while keeping it consistent with the English documentation. Make this change in
the README table row that lists `ColorGenInput` so the parameter naming remains
accurate and aligned with the source API.
---
Nitpick comments:
In `@README.zh-CN.md`:
- Line 39: The feature description in README.zh-CN.md is still in English and
should be fully translated to Chinese. Update the `Color` helpers sentence so it
consistently uses Chinese wording while preserving the meaning of hex, RGB, and
HSB conversions, and keep the `Color` reference recognizable in the translated
text.
- Around line 93-99: The Color method descriptions in the README.zh-CN table are
still in English and should be translated to match the “说明” column. Update the
entries for toHexString, toHsb, toHsbString, toRgb, and toRgbString in the
README.zh-CN.md table so their descriptions are Chinese equivalents, keeping the
method names and type signatures unchanged.
🪄 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: 5d42e89d-a84c-400b-8cbb-6211099fd70c
⛔ Files ignored due to path filters (1)
tests/__snapshots__/index.test.tsx.snapis excluded by!**/*.snap
📒 Files selected for processing (12)
.dumirc.ts.github/FUNDING.yml.github/workflows/main.yml.github/workflows/preview.yml.github/workflows/react-doctor.yml.github/workflows/surge-preview.ymlREADME.mdREADME.zh-CN.mdpackage.jsontests/setup.tstsconfig.jsonvercel.json
💤 Files with no reviewable changes (1)
- .github/workflows/preview.yml
1 participant
Summary
Standardize this rc-component repository as part of the Ant Design rc-component maintenance sweep.
Tracking issue: ant-design/ant-design#58514
Scope
types: "./es/index.d.ts", publishConfig, and release flow through@rc-component/np.react-component/rc-test/.github/workflows/test-utoo.yml@mainworkflow, React Doctor, Codecov, CodeQL, updated GitHub Actions versions, and guarded Surge preview fallback.docs-distoutput and remove legacynow-build/ Cloudflare Pages residue.Notes
secrets: inheritis kept untilreact-component/rc-test#176is merged, then it can be narrowed to explicitCODECOV_TOKENforwarding.Summary by CodeRabbit
New Features
Bug Fixes
Chores