test: use unified github action yml

[Layouwen]

ant-design/ant-design#50461

Summary by CodeRabbit

• New Features

  • Introduced a new bunfig.toml configuration file for improved dependency management.
  • Updated testing scripts to provide options for one-off test runs and continuous watch mode.

• Chores

  • Streamlined the GitHub Actions workflow by consolidating multiple jobs into a single test job.
  • Added bun.lockb to the .gitignore file to manage ignored files effectively.

• Bug Fixes

  • Updated the main testing script to disable watch mode by default, improving test execution control.

[coderabbitai]

Walkthrough

The changes involve restructuring the GitHub Actions workflow by replacing multiple jobs with a single external workflow for testing. A new .gitignore entry is added to exclude bun.lockb, while a bunfig.toml file is introduced to manage package installation parameters. Additionally, the package.json file updates testing scripts to provide options for running tests in watch mode or one-off execution.

Changes

File	Change Summary
.github/workflows/main.yml	Replaced multiple jobs with a single test job using an external workflow for testing.
`.gitignore	Added bun.lockb to ignore list.
`bunfig.toml	Introduced with peer = false to manage package installations.
`package.json	Updated test scripts to include --watch=false and added a new test:watch script.

Poem

🐰 In the meadow where code does play,
Changes hop in a joyful ballet.
With scripts so swift and workflows neat,
Our project dances on tiny feet!
Let’s embrace the new, say hooray,
For brighter days in the coding fray! 🌼

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.07%. Comparing base (880ed09) to head (5ddc380).
Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #194   +/-   ##
=======================================
  Coverage   95.07%   95.07%           
=======================================
  Files          33       33           
  Lines        2883     2883           
  Branches      456      456           
=======================================
  Hits         2741     2741           
  Misses        142      142           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 880ed09 and 5ddc380.

Files selected for processing (4)

• .github/workflows/main.yml (1 hunks)
• .gitignore (1 hunks)
• bunfig.toml (1 hunks)
• package.json (1 hunks)

Files skipped from review due to trivial changes (3)

• .github/workflows/main.yml
• .gitignore
• bunfig.toml

Additional comments not posted (2)

package.json (2)

39-39: LGTM: Update to the "test" script.

The addition of --watch=false to the "test" script is appropriate for CI environments, ensuring tests run once without watching for changes.

---

40-40: LGTM: Addition of the "test:watch" script.

Introducing a "test:watch" script is a good practice, allowing developers to run tests in watch mode during local development.