test: just test

[huntye1]

Summary by CodeRabbit

Release Notes

• New Features

  • Introduced a GitHub Action to synchronize events with a Lark group, sending notifications for pull requests, issues, and CI failures.
  • Added a README file detailing the new action and its usage.
  • Created a workflow for event synchronization triggered by specific GitHub events.

• Bug Fixes

  • Removed the previous workflow that sent notifications to Feishu, streamlining event handling.

• Documentation

  • Added comprehensive documentation for the new event synchronization action.

• Configuration

  • Established new TypeScript and ESLint configurations for improved development practices.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request introduces a new GitHub Action named @coze-infra/event-sync-action, which synchronizes GitHub events with a Lark group. It includes various components such as a README file, configuration files, TypeScript interfaces, and event handlers for managing notifications related to pull requests, issues, and CI failures. Additionally, it establishes workflows for event synchronization and modifies existing configurations to support this new functionality.

Changes

File	Change Summary
.github/actions/event-sync/README.md	New README for @coze-infra/event-sync-action describing its functionality and usage.
.github/actions/event-sync/action.yml	Added action definition with name, description, input parameter (webhook_url), and Node.js configuration.
.github/actions/event-sync/config/rush-project.json	New Rush configuration file defining operations for testing and building.
.github/actions/event-sync/eslint.config.cjs	New ESLint configuration for Node.js, excluding the lib/** directory from linting.
.github/actions/event-sync/lib/package.json	New package.json specifying module type as ECMAScript modules.
.github/actions/event-sync/package.json	New package.json for the action with metadata, scripts, and dependencies.
.github/actions/event-sync/src/handlers/event-handler.ts	Introduced EventHandler class and subclasses for handling GitHub events.
.github/actions/event-sync/src/handlers/handler-factory.ts	Added handlerFactory with createHandler method to instantiate event handlers.
.github/actions/event-sync/src/index.js	New entry file utilizing TypeScript support for dynamic imports.
.github/actions/event-sync/src/index.ts	New asynchronous run function as the main entry point for handling events.
.github/actions/event-sync/src/platforms/lark.ts	New LarkPlatform class for sending notifications to Lark.
.github/actions/event-sync/src/types.ts	Introduced NotificationMessage and NotificationPlatform interfaces for typing.
.github/actions/event-sync/tsconfig.build.json	New TypeScript build configuration file.
.github/actions/event-sync/tsconfig.json	New TypeScript configuration with project references and module settings.
.github/actions/event-sync/tsconfig.misc.json	New TypeScript configuration extending base settings for test directories.
.github/actions/event-sync/vitest.config.ts	New Vitest configuration file for testing setup.
.github/workflows/event-sync.yml	New workflow for synchronizing events with Lark, triggered by specific GitHub events.
.github/workflows/lark-sync.yml	Removed workflow for notifying Feishu about issues and PRs.
rush.json	Added new project entry for @coze-infra/event-sync-action.

Possibly related PRs

• chore: sync events to lark #32: Introduces a new GitHub Actions workflow to synchronize events with a Feishu group, related to the notification functionality.
• perf: Optimize real-time demo #15: Enhances real-time demo with functionality for event handling, which may relate to the notification features.
• feat: improve TypeScript support #18: Improves TypeScript support, relevant due to the introduction of new TypeScript files and configurations in this PR.

Suggested reviewers

• jsongo

🐰 In the garden where events bloom,
A sync to Lark dispels the gloom.
With PRs and issues, notifications fly,
A hop, a skip, as messages sigh.
So gather 'round, let the actions play,
In our coding burrow, we celebrate today! 🌼✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 2a94278 and 78d39c6.

⛔ Files ignored due to path filters (1)

• common/config/subspaces/default/pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (19)

• .github/actions/event-sync/README.md (1 hunks)
• .github/actions/event-sync/action.yml (1 hunks)
• .github/actions/event-sync/config/rush-project.json (1 hunks)
• .github/actions/event-sync/eslint.config.cjs (1 hunks)
• .github/actions/event-sync/lib/package.json (1 hunks)
• .github/actions/event-sync/package.json (1 hunks)
• .github/actions/event-sync/src/handlers/event-handler.ts (1 hunks)
• .github/actions/event-sync/src/handlers/handler-factory.ts (1 hunks)
• .github/actions/event-sync/src/index.js (1 hunks)
• .github/actions/event-sync/src/index.ts (1 hunks)
• .github/actions/event-sync/src/platforms/lark.ts (1 hunks)
• .github/actions/event-sync/src/types.ts (1 hunks)
• .github/actions/event-sync/tsconfig.build.json (1 hunks)
• .github/actions/event-sync/tsconfig.json (1 hunks)
• .github/actions/event-sync/tsconfig.misc.json (1 hunks)
• .github/actions/event-sync/vitest.config.ts (1 hunks)
• .github/workflows/event-sync.yml (1 hunks)
• .github/workflows/lark-sync.yml (0 hunks)
• rush.json (1 hunks)

---

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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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 using 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.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

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.