chore: standardize repository config - #319
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
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 (14)
Walkthrough本次变更统一调整文档站输出目录与发布路径，新增和更新多个 GitHub Actions 工作流，并重写 README 与资助配置以匹配新的仓库信息。 Changes站点构建与仓库自动化更新
Estimated code review effort🎯 4 (Complex) | ⏱️ ~45 minutes 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 |
✅ Preview is ready!
↩️ Previous: ⚡️ 🤖 Powered by surge-preview |
|||||||||||||||
![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 updates the project configuration and documentation to support the scoped package @rc-component/mentions. Key changes include updating the build output directory to docs-dist, adding Vercel deployment configuration, introducing helper scripts in package.json, and rewriting the README.md to reflect the new package name, APIs, and usage examples. Feedback is provided regarding a duplicate .vercel entry in the .gitignore file.
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.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #319 +/- ##
=======================================
Coverage 98.33% 98.33%
=======================================
Files 8 8
Lines 301 301
Branches 79 77 -2
=======================================
Hits 296 296
Misses 5 5 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🧹 Nitpick comments (1)
.github/workflows/react-doctor.yml (1)
27-27: 🔒 Security & Privacy | 🔵 Trivial确认
millionco/react-doctor的令牌配置与 Fork PR 支持限制。
github-token并非必填输入，该 Action 会自动使用工作流的内置令牌（${{ github.token }}）来发布评论和状态检查。显式传入该参数是可选的，主要用于更精细的控制。然而，对于来自 fork 仓库的
pull_request事件，GitHub 的内置令牌默认是只读的。即使在工作流中配置了permissions写入权限，也无法绕过此限制。在此场景下，该 Action 将无法发布或更新 Pull Request 评论（静默失败），尽管代码扫描本身仍可正常进行。若您的协作流程包含大量外部贡献者的 fork PR，请知悉此限制。🤖 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/react-doctor.yml at line 27, The react-doctor workflow step may fail silently on forked pull_request events because it relies on the default github.token, which is read-only for forks. Update the workflow entry using millionco/react-doctor to either explicitly configure a suitable github-token for trusted contexts or gate/comment-disable the review-posting behavior for fork PRs, so the action still runs without attempting to post or update comments when permissions are insufficient.
🤖 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 @.dumirc.ts:
- Around line 5-10: The isProdSite logic is incorrectly inferring GitHub Pages
from GITHUB_ACTIONS, which causes non-Pages CI builds to use the production
base/public path. Update the .dumirc.ts path selection so isProdSite depends
only on the explicit GH_PAGES flag, and keep basePath and publicPath derived
from that single source of truth. This will prevent ordinary GitHub Actions
builds from emitting /${name}/ asset URLs unless GH_PAGES=1 is set.
In `@package.json`:
- Around line 37-39: The release flow is split incorrectly because `postpublish`
runs after `npm publish` and can fail independently, leaving the package
published but the overall release marked failed. Remove the `postpublish` hook
from the package scripts and move the `npm run gh-pages` step into a separate
release/workflow stage so `npm publish` and Pages deployment are handled as
independent steps; use the existing `prepublishOnly`, `prettier`, and `gh-pages`
script entries to locate the change.
In `@README.md`:
- Around line 91-128: The API table for MentionsProps should not reference
MentionsProps['classNames'] and MentionsProps['styles'] because it hides the
actual shape and creates a circular/self-referential description. Update the
README entry for classNames and styles to expand the concrete slot structures
from the implementation in Mentions so readers can see the exact fields
available. Keep the rest of the table unchanged and make the descriptions match
the real definitions exposed by the component.
---
Nitpick comments:
In @.github/workflows/react-doctor.yml:
- Line 27: The react-doctor workflow step may fail silently on forked
pull_request events because it relies on the default github.token, which is
read-only for forks. Update the workflow entry using millionco/react-doctor to
either explicitly configure a suitable github-token for trusted contexts or
gate/comment-disable the review-posting behavior for fork PRs, so the action
still runs without attempting to post or update comments when permissions are
insufficient.
🪄 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: 714edd43-91c8-456e-83df-513642df1482
📒 Files selected for processing (10)
.dumirc.ts.github/FUNDING.yml.github/workflows/codeql.yml.github/workflows/react-component-ci.yml.github/workflows/react-doctor.yml.github/workflows/surge-preview.yml.gitignoreREADME.mdpackage.jsonvercel.json
|
Deployment failed with the following error: Learn More: https://vercel.com/afc163s-projects?upgradeToPro=build-rate-limit |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
2 participants
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.