Remove bors and use GitHub merge queue

[curquiza]

✅ Settings update to include merge queue

Summary by CodeRabbit

• Documentation
  • Updated code formatting in README examples for improved readability.

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

[coderabbitai]

Walkthrough

These changes remove references to Bors bot automation tooling and associated documentation about PR rebase/merge automation and changelog generation, while updating CI/CD triggers to use merge_group instead of explicit branch filters.

Changes

Cohort / File(s)	Summary
Configuration & Workflow Updates .github/release-draft-template.yml, .github/workflows/tests.yml	Removed @bors-related replacer rules from release template; replaced branch-specific push triggers (trying, staging, main) with merge_group trigger in test workflow.
Documentation Removals CONTRIBUTING.md	Removed sections describing PR automation (up-to-date requirement, rebase/merge automation, automated changelog generation) from Release Process guidance.
Documentation Formatting README.md	Removed Bors badge line; reformatted code example block for improved layout alignment.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• The changes are primarily configuration removals and documentation updates with straightforward intent.
• The workflow trigger change (merge_group vs. branch filters) warrants confirmation that it aligns with intended CI/CD behavior.

Poem

🐰 With Bors now gone, our workflows flow,
Merge groups guide the way we go,
Docs trimmed clean, like freshly groomed fur,
Our processes lighter—watch us whir! ✨

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' accurately summarizes the main change across the pull request, which involves removing bors bot references and replacing push-based CI triggers with GitHub's merge_group trigger.
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 a3bb5f3 and 5fb0c4b.

📒 Files selected for processing (4)

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

💤 Files with no reviewable changes (2)

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

🔇 Additional comments (2)

.github/workflows/tests.yml (1)

8-8: Correctly added merge_group trigger for GitHub merge queue.

The merge_group trigger properly enables GitHub Actions workflows to run when PRs are queued for merge via the merge queue, replacing the Bors automation approach.

README.md (1)

202-205: Documentation update is clear and maintains accurate example.

The code example formatting change improves readability by restructuring the method chain. The example remains functionally accurate and demonstrates the correct API usage pattern.

---

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

[brunoocasali]

LGTM!