chore: standardize repository setup#299
Conversation
❌ Deploy failed
📋 Build log (last lines)🤖 Powered by surge-preview |
|||||||||
|
Warning Review limit reached
More reviews will be available in 18 minutes and 25 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 (7)
Walkthrough更新了 README、脚本和中文文档，新增资助与预览部署配置，并调整了 CodeQL、复用测试、React Doctor 和 Surge preview 工作流。 Changes仓库文档与自动化
CI 检查与预览部署
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 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 |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #299 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 1 1
Lines 30 30
Branches 5 5
=========================================
Hits 30 30 ☔ 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 updates the repository configuration and documentation to align with the @rc-component/checkbox package. Key changes include adding a funding configuration, updating the README with modern examples and API tables, adding a Vercel deployment configuration, and adjusting scripts in package.json (such as switching from bunx to standard tsc and adding --ignore-unknown to Prettier). The reviewer suggested simplifying the lint-staged Prettier command for TypeScript files by removing the redundant --parser=typescript flag, which is already automatically inferred by Prettier.
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.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
package.json (1)
42-46: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value
--ignore-unknown与显式--parser=typescript的组合说明。Line 45-46 中，
*.ts?(x)的 Prettier 命令同时使用了--parser=typescript和--ignore-unknown。由于已显式指定解析器，--ignore-unknown对该匹配模式实际上不会生效（Prettier 已知如何处理），但也不会产生副作用。如果目的是统一配置风格，可以保留；若想精简，可移除该模式下的--ignore-unknown。🤖 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 `@package.json` around lines 42 - 46, The `*.ts?(x)` Prettier task in package.json redundantly combines `--parser=typescript` with `--ignore-unknown`; since the parser is already explicit, simplify that matcher by removing the unnecessary `--ignore-unknown` flag while keeping the TypeScript parser command intact. Update the `*.ts?(x)` entry only, leaving the other glob patterns 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 call in the main GitHub Actions config
is using an unpinned ref and inheriting all secrets, which should be tightened.
Update the workflow reference to a specific commit SHA instead of `@main`, and
replace secrets: inherit with an explicit secret mapping that passes only
CODECOV_TOKEN to the reused workflow. Use the existing workflow call entry to
locate and adjust this external reuse configuration.
---
Nitpick comments:
In `@package.json`:
- Around line 42-46: The `*.ts?(x)` Prettier task in package.json redundantly
combines `--parser=typescript` with `--ignore-unknown`; since the parser is
already explicit, simplify that matcher by removing the unnecessary
`--ignore-unknown` flag while keeping the TypeScript parser command intact.
Update the `*.ts?(x)` entry only, leaving the other glob patterns 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: 0a42061e-32d7-4f8a-9f4c-ecbf0b7342b2
📒 Files selected for processing (9)
.github/FUNDING.yml.github/workflows/cloudflare-pages-preview.yml.github/workflows/codeql.yml.github/workflows/main.yml.github/workflows/react-doctor.yml.github/workflows/surge-preview.ymlREADME.mdpackage.jsonvercel.json
|
AI review follow-up:
|
There was a problem hiding this comment.
Actionable comments posted: 5
🤖 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/surge-preview.yml:
- Around line 36-38: The “Skip Surge preview” step still has an incorrect
conditional and needs the same fix applied to the `if` expression used by that
step. Update the `Skip Surge preview` job step so it checks the Surge token
condition consistently with the workflow’s secret handling, and ensure the `if`
on the `Skip Surge preview` step is corrected together with the surrounding
preview logic.
- Around line 36-38: The “Skip Surge preview” workflow step is still using the
invalid secrets context in its if condition; update the step’s condition to use
the correct context pattern consistent with the rest of the workflow. Make the
same change in the Skip Surge preview step so the secret check is evaluated
without directly referencing secrets in the if expression.
- Around line 21-35: The step-level conditions in the surge-preview workflow are
using the invalid secrets context, so fix the Build preview step and the
afc163/surge-preview action to stop referencing secrets.SURGE_TOKEN directly in
their if clauses. Move SURGE_TOKEN to a job-level env and update the if checks
to use env.SURGE_TOKEN instead, keeping the existing build and surge-preview
configuration intact.
- Around line 21-35: The step-level condition in the workflow is using the
unsupported secrets context, which breaks validation for the Build preview and
surge-preview steps. Move SURGE_TOKEN to a job-level env so both the build step
and the afc163/surge-preview action can read it, then change the existing if
conditions to check the env context instead of secrets. Use the Build preview
step and afc163/surge-preview action as the places to update.
In `@README.zh-CN.md`:
- Around line 80-102: Checkbox 和 Ref 的 API 表格里把英文标识符误翻成了中文，需在 README.zh-CN.md
的相关表格中把 `风格` 改回 `style`、`价值` 改回 `value`、`模糊` 改回 `blur`、`重点` 改回
`focus`，并顺手统一这些条目的描述排版与空格；同时把“本机输入属性”改为“原生输入属性”，确保表格里的参数名与 `Checkbox`、`Ref` 里真实的
API 名称一致。
🪄 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: d89e8c11-4d1e-4576-90a5-bcf0c058fda1
📒 Files selected for processing (3)
.github/workflows/surge-preview.ymlREADME.mdREADME.zh-CN.md
✅ Files skipped from review due to trivial changes (1)
- README.md
|
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.
|
1 participant
Summary
react-component/rc-test/.github/workflows/test-utoo.yml@main.tsc, Prettier, and Husky.Verification
Summary by CodeRabbit
新功能
dist。文档
维护
Refs ant-design/ant-design#58514