chore: enable checks being run on merge queue

[adu-web3]

Description

As described in comment #66 (comment), the checks would not be re-run when another pull request gets merged before merging a pull request. To enable checks being automatically re-run even if no new commit is pushed, we have set the main branch protection rules to require merge queue, and this pull request add merge_group to workflow files to trigger these checks for merge queue

Summary by CodeRabbit

• New Features
  • Introduced a new event trigger, merge_group, to the CI workflows, enhancing responsiveness to specific repository activities.
  • Improved the execution of the linter and Slither analysis by adding support for the merge_group event.

These changes provide more granular control over when CI processes run, potentially improving workflow efficiency and issue detection.

[coderabbitai]

Walkthrough

The recent updates enhance the GitHub Actions workflows by adding a new event trigger, merge_group, to three files: forge-ci.yml, lint.yml, and slither.yml. This addition allows the continuous integration (CI) process to respond to merge group events, improving responsiveness and flexibility in handling repository activities, while maintaining the existing functionality for pull requests and pushes.

Changes

Files	Change Summary
.github/workflows/forge-ci.yml, .github/workflows/lint.yml, .github/workflows/slither.yml	Added merge_group event trigger to improve CI responsiveness and expand conditions for workflow execution.

Poem

🐇 In the land of code where bunnies hop,
New triggers sprout, never let them stop!
Merge groups now dance in CI's bright light,
Making workflows nimble, oh what a delight!
With every new change, we cheer and we play,
Hopping through code on this fine, sunny day! 🌼

---

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.

[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 29f2982 and b31e600.

Files selected for processing (3)

• .github/workflows/forge-ci.yml (1 hunks)
• .github/workflows/lint.yml (1 hunks)
• .github/workflows/slither.yml (1 hunks)

Additional comments not posted (3)

.github/workflows/slither.yml (1)

4-4: LGTM!

The addition of the merge_group trigger is correct and enhances the workflow's responsiveness.

.github/workflows/lint.yml (1)

4-4: LGTM!

The addition of the merge_group trigger is correct and enhances the workflow's responsiveness.

.github/workflows/forge-ci.yml (1)

5-5: LGTM!

The addition of the merge_group trigger is correct and enhances the workflow's responsiveness.