chore(ci): Prepare to switch to Merge Queue for PR merging

[MaxymVlasov]

Description of your changes

I previously tried to automate Renovate PR merges, but it works poorly, plus it's time to time violate review process.

So, to address known issues with time-consuming merge of many Renovate PRs at once, make OpenSSF scorecard happier in terms of branch protection rules (#712) and make finally get ability to merge many Renovate PRs at once - let's enable Merge queue for PRs.
For this, required:

1. Merge this PR
2. Change branch protection ruleset slightly (will send instructions to Anton later)
3. Enable Merge Queue in repo settings.
   UPD. Merge Queue is accessible only for organizations... So we're can't use it right now, but I'll merge it anyway in case if we will migrate to organization one day

[coderabbitai]

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Expanded GitHub Actions workflows to also run on merge group events, in addition to pull request events. This affects build, CodeQL analysis, dependency review, and pre-commit workflows. No changes to workflow logic or jobs.

Walkthrough

The GitHub Actions workflow trigger configurations were updated across several workflow files to include the merge_group event. This change ensures that workflows are now triggered not only by pull requests but also by merge group events. No modifications were made to workflow logic, jobs, or steps.

Changes

File(s)	Change Summary
.github/workflows/build-image-test.yaml	Added merge_group as a workflow trigger event.
.github/workflows/codeql.yml	Added merge_group as a workflow trigger event.
.github/workflows/dependency-review.yml	Added merge_group as a workflow trigger event.
.github/workflows/pre-commit.yaml	Added merge_group as a workflow trigger event.

Suggested reviewers

• antonbabenko
• yermulnik

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3dd96e2 and 72095ed.

📒 Files selected for processing (4)

• .github/workflows/build-image-test.yaml (1 hunks)
• .github/workflows/codeql.yml (1 hunks)
• .github/workflows/dependency-review.yml (1 hunks)
• .github/workflows/pre-commit.yaml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Ubuntu x64

🔇 Additional comments (4)

.github/workflows/dependency-review.yml (1)

13-14: Approve addition of merge_group trigger
The workflow now correctly listens to merge_group events in addition to pull_request, aligning with the Merge Queue setup. No further changes needed here.

.github/workflows/build-image-test.yaml (1)

4-5: Approve addition of merge_group trigger
This workflow will now run under Merge Queue events as intended, while preserving the existing pull_request trigger.

.github/workflows/pre-commit.yaml (1)

4-5: Approve addition of merge_group trigger
The pre-commit job will now be invoked for Merge Queue merges, ensuring branch protection compliance.

.github/workflows/codeql.yml (1)

18-18: Approve addition of merge_group trigger
CodeQL analysis is now correctly configured to run on Merge Queue events as well.

---

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.

❤️ 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

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.

[Copilot]

Pull Request Overview

Adds the merge_group trigger to existing GitHub workflows so they run when using the Merge Queue feature.

• Introduce merge_group event alongside pull_request for CI jobs
• Ensure pre-commit checks, dependency review, CodeQL, and Docker smoke tests cover Merge Queue merges

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.

File	Description
.github/workflows/pre-commit.yaml	Add merge_group trigger to pre-commit checks
.github/workflows/dependency-review.yml	Add merge_group trigger to dependency review
.github/workflows/codeql.yml	Add merge_group trigger to CodeQL workflow
.github/workflows/build-image-test.yaml	Add merge_group trigger to Docker build tests

[yermulnik]

Copilot highlighted an interesting point: GHA docs say «specifying the activity type will keep your workflow specific if more activity types are added in the future» — why would you want to rely upon the assumption that activity types, added in future, will match the purpose of what you're implementing tin this PR? 🤔

ps: when you resolve PR review comments w/o any type of feedback (comment or commit), it produces more questions than answers =)

[antonbabenko]

This PR is included in version 1.99.1 🎉