chore: standardize repository maintenance#81
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
✅ Preview is ready!
↩️ Previous: ⚡️ 🤖 Powered by surge-preview |
|||||||||||||||
|
Warning Review limit reached
Next review available in: 58 minutes Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable usage-based reviews in Billing to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). How can I continue?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 reviews. How do review 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, and refer to the rate limits docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
Walkthrough此 PR 将文档站点输出目录从 Changes文档站点与仓库自动化
Estimated code review effort🎯 2 (Simple) | ⏱️ ~15 minutes Suggested reviewers
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 |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #81 +/- ##
=======================================
Coverage 98.09% 98.09%
=======================================
Files 11 11
Lines 421 421
Branches 121 119 -2
=======================================
Hits 413 413
Misses 7 7
Partials 1 1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Code Review
This pull request updates the project's build, documentation, and deployment configurations, including transitioning the documentation output directory to docs-dist, adding a Vercel configuration, and modernizing the README. It also updates the TypeScript path mappings for the dumi temporary directory. The feedback points out that excluding the .dumi directory in tsconfig.json will prevent TypeScript from resolving the generated type definitions under .dumi/tmp/*, and suggests removing it from the exclusion list.
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.
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (2)
.github/workflows/cloudflare-pages-preview.yml (1)
26-41: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value重复的密钥校验条件可合并为作业级 guard。
Install dependencies、Build site、Deploy preview三步重复了完全相同的三元条件表达式,Skip步骤则是其取反。后续若新增配置项(如再加一个变量),需要同步修改 4 处,易遗漏。建议在job级别用outputs或单独的判断步骤集中处理,例如:♻️ 建议的重构方向
preview: runs-on: ubuntu-latest env: CLOUDFLARE_API_TOKEN: ${{ secrets.CLOUDFLARE_API_TOKEN }} CLOUDFLARE_ACCOUNT_ID: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }} CLOUDFLARE_PAGES_PROJECT: ${{ vars.CLOUDFLARE_PAGES_PROJECT }} PREVIEW: true steps: - uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 with: persist-credentials: false + - name: Check configuration + id: cfg + run: | + if [ -n "$CLOUDFLARE_API_TOKEN" ] && [ -n "$CLOUDFLARE_ACCOUNT_ID" ] && [ -n "$CLOUDFLARE_PAGES_PROJECT" ]; then + echo "enabled=true" >> "$GITHUB_OUTPUT" + else + echo "Cloudflare Pages preview is not configured; skip deployment." + echo "enabled=false" >> "$GITHUB_OUTPUT" + fi - name: Install dependencies - if: ${{ env.CLOUDFLARE_API_TOKEN != '' && env.CLOUDFLARE_ACCOUNT_ID != '' && env.CLOUDFLARE_PAGES_PROJECT != '' }} + if: ${{ steps.cfg.outputs.enabled == 'true' }} run: npm install🤖 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 @.github/workflows/cloudflare-pages-preview.yml around lines 26 - 41, The Cloudflare Pages preview workflow repeats the same secret-check condition across multiple steps, while the skip step uses the inverse, making the logic hard to maintain. Consolidate the configuration check into a single job-level guard or one dedicated condition step in cloudflare-pages-preview.yml, then have Install dependencies, Build site, and Deploy preview reuse that shared result instead of duplicating the expression..github/workflows/codeql.yml (1)
3-9: 🚀 Performance & Scalability | 🔵 Trivial | 💤 Low value建议补充并发控制以取消过期运行。
本 PR 为其它诊断工作流(如
react-doctor.yml)添加了concurrency控制,但 CodeQL 工作流缺少同样配置。在频繁推送时会并行跑多次分析,浪费 runner 资源。建议添加:♻️ 建议补充
on: push: branches: ['master'] pull_request: branches: ['master'] schedule: - cron: '24 18 * * 1' + +concurrency: + group: codeql-${{ github.event.pull_request.number || github.ref }} + cancel-in-progress: true🤖 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 @.github/workflows/codeql.yml around lines 3 - 9, CodeQL workflow is missing the same concurrency cancellation behavior used elsewhere, so repeated pushes can leave stale runs executing in parallel. Update the workflow definition in the CodeQL configuration to add a concurrency group that keys off the workflow/ref context and enables cancellation of in-progress older runs, using the existing workflow structure near the trigger configuration.
🤖 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/react-component-ci.yml:
- Around line 7-8: The reusable workflow invocation in react-component-ci is
over-sharing secrets and should be tightened. In the workflow call that uses
test-utoo.yml, remove secrets: inherit and pass only the CODECOV_TOKEN
explicitly, since that is the only secret the downstream workflow needs. Also
update the workflow reference from `@main` to a specific commit SHA if possible to
reduce supply-chain risk; if SHA pinning is not available yet, still ensure the
secret scope is limited in the call site.
In `@README.md`:
- Around line 130-150: The Release section in README is inaccurate: `npm run
prepublishOnly` is only a pre-publish hook and does not perform the actual
release with `@rc-component/np`. Update the release instructions to point to the
real publish/release command used by the project (such as the
`release`/`publish` script or invoking `@rc-component/np` directly) and keep the
Development command list unchanged.
---
Nitpick comments:
In @.github/workflows/cloudflare-pages-preview.yml:
- Around line 26-41: The Cloudflare Pages preview workflow repeats the same
secret-check condition across multiple steps, while the skip step uses the
inverse, making the logic hard to maintain. Consolidate the configuration check
into a single job-level guard or one dedicated condition step in
cloudflare-pages-preview.yml, then have Install dependencies, Build site, and
Deploy preview reuse that shared result instead of duplicating the expression.
In @.github/workflows/codeql.yml:
- Around line 3-9: CodeQL workflow is missing the same concurrency cancellation
behavior used elsewhere, so repeated pushes can leave stale runs executing in
parallel. Update the workflow definition in the CodeQL configuration to add a
concurrency group that keys off the workflow/ref context and enables
cancellation of in-progress older runs, using the existing workflow structure
near the trigger configuration.
🪄 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: 3d81783f-fdee-4a12-b328-620c6fc25aaf
📒 Files selected for processing (14)
.dumirc.ts.github/FUNDING.yml.github/workflows/cloudflare-pages-preview.yml.github/workflows/codeql.yml.github/workflows/main.yml.github/workflows/react-component-ci.yml.github/workflows/react-doctor.yml.github/workflows/surge-preview.yml.gitignoreREADME.mdnow.jsonpackage.jsontsconfig.jsonvercel.json
💤 Files with no reviewable changes (2)
- now.json
- .github/workflows/main.yml
|
Deployment failed with the following error: Learn More: https://vercel.com/afc163s-projects?upgradeToPro=build-rate-limit |
|
Deployment failed with the following error: Learn More: https://vercel.com/react-component?upgradeToPro=build-rate-limit |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|

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
Documentation
Chores