Remove bors and use GitHub merge queue

[curquiza]

Ruleset set up for the usage of GitHub merge queue ✅

Summary by CodeRabbit

• Documentation

  • Updated contribution guidelines with new automated changelog process information.
  • Minor formatting and whitespace improvements in README.

• Chores

  • Updated CI/CD workflow configuration for improved build processes.
  • Modified release template configuration.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Repository automation configuration and documentation are updated to remove Bors bot integration references. The changelog template stops filtering bot mentions, the workflow configuration simplifies branch filters and adds merge_group event support, and contributor documentation is updated to reflect changes in PR automation processes.

Changes

Cohort / File(s)	Summary
Release & Workflow Configuration .github/release-draft-template.yml, .github/workflows/tests.yml	Removed replacer rules for @bors and @meili-bors mentions in changelog generation; simplified workflow branch filters (removed trying and staging, kept main); added merge_group event trigger.
Documentation CONTRIBUTING.md, README.md	Updated contribution guidelines to remove Bors-related PR rebase enforcement guidance and added new "Automated Changelogs" subsection; removed Bors badge and applied minor whitespace/formatting cleanups to README examples.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• No logic changes or functional impact; purely configuration and documentation updates
• Changes are straightforward removals and additions of text/configuration lines
• No interdependencies or complex interactions to verify

Poem

A Bors bot no more shall grace these halls, 🐰
Its mentions now speak freely in the changelogs' calls,
Workflows simplified, merge_group now flows,
New changelog paths in the docs that compose,
Rabbit bounces forth with cleaner prose! 🐇✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Remove bors and use GitHub merge queue' directly and clearly summarizes the main changes across the PR, which involve removing bors-related configuration and implementing GitHub merge queue.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch remove-bors

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 16e4d4b and 7ebeda9.

📒 Files selected for processing (4)

• .github/release-draft-template.yml (0 hunks)
• .github/workflows/tests.yml (1 hunks)
• CONTRIBUTING.md (0 hunks)
• README.md (5 hunks)

💤 Files with no reviewable changes (2)

• .github/release-draft-template.yml
• CONTRIBUTING.md

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (7)

• GitHub Check: integration-tests (Rails 7 with Ruby 3.4)
• GitHub Check: integration-tests (Rails 6.1 with Ruby 3.4)
• GitHub Check: integration-tests (Rails 7 with Ruby 3.3)
• GitHub Check: integration-tests (Rails 7 with Ruby 3.2)
• GitHub Check: integration-tests (Rails 6.1 with Ruby 3.2)
• GitHub Check: integration-tests (Rails 6.1 with Ruby 3.3)
• GitHub Check: smoke-test

🔇 Additional comments (2)

README.md (1)

1-1123: No blocking issues identified. Changes align with PR objectives.

This README update supports the migration from Bors to GitHub merge queue with cosmetic adjustments (minor formatting and whitespace tweaks). The changes maintain all documentation accuracy and functionality without introducing breaking changes.

.github/workflows/tests.yml (1)

8-8: Verify that github.base_ref is available in merge_group event context.

Adding the merge_group event trigger is correct for GitHub merge queue integration. However, the job conditional at line 14 references github.base_ref, which may not be available or may behave differently in merge_group event contexts compared to pull_request events.

Please verify that the conditional logic at line 14 works correctly with merge_group events by either:

1. Testing the workflow with a merge queue (if possible in your environment), or
2. Confirming against GitHub Actions documentation that github.base_ref is available in merge_group contexts.

If github.base_ref is not available for merge_group events, the condition may need to be updated to:

if: github.event_name != 'pull_request' || !startsWith(github.base_ref, 'bump-meilisearch-v')

or split into separate conditional blocks per event type.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.69%. Comparing base (16e4d4b) to head (7ebeda9).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #433   +/-   ##
=======================================
  Coverage   90.69%   90.69%           
=======================================
  Files          14       14           
  Lines         849      849           
=======================================
  Hits          770      770           
  Misses         79       79           

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.