diff --git a/.github/release-draft-template.yml b/.github/release-draft-template.yml
index 0ec349d..69ea558 100644
--- a/.github/release-draft-template.yml
+++ b/.github/release-draft-template.yml
@@ -29,7 +29,5 @@ template: |
 no-changes-template: 'Changes are coming soon 😎'
 sort-direction: 'ascending'
 replacers:
-  - search: '/(?:and )?@bors(?:\[bot\])?,?/g'
-    replace: ''
   - search: '/(?:and )?@meili-bot,?/g'
     replace: ''
diff --git a/.github/workflows/tests.yml b/.github/workflows/tests.yml
index 7272696..f182e14 100644
--- a/.github/workflows/tests.yml
+++ b/.github/workflows/tests.yml
@@ -3,11 +3,9 @@ name: Tests
 on:
   pull_request:
   push:
-    # trying and staging branches are for BORS config
     branches:
-      - trying
-      - staging
       - main
+  merge_group:
 
 env:
   MEILISEARCH_URL: http://localhost:7700
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 6045b1c..00baef3 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -141,7 +141,6 @@ Some notes on GitHub PRs:
 
 - [Convert your PR as a draft](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request) if your changes are a work in progress: no one will review it until you pass your PR as ready for review.<br>
   The draft PR can be very useful if you want to show that you are working on something and make your work visible.
-- The branch related to the PR must be **up-to-date with `main`** before merging. Fortunately, this project [integrates a bot](https://github.com/meilisearch/integration-guides/blob/main/resources/bors.md) to automatically enforce this requirement without the PR author having to do it manually.
 - All PRs must be reviewed and approved by at least one maintainer.
 - The PR title should be accurate and descriptive of the changes. The title of the PR will be indeed automatically added to the next [release changelogs](https://github.com/meilisearch/meilisearch-dart/releases/).
 
@@ -149,11 +148,6 @@ Some notes on GitHub PRs:
 
 Meilisearch tools follow the [Semantic Versioning Convention](https://semver.org/).
 
-### Automation to Rebase and Merge the PRs <!-- omit in TOC -->
-
-This project integrates a bot that helps us manage pull requests merging.<br>
-_[Read more about this](https://github.com/meilisearch/integration-guides/blob/main/resources/bors.md)._
-
 ### Automated Changelogs <!-- omit in TOC -->
 
 This project integrates a tool to create automated changelogs.<br>
diff --git a/README.md b/README.md
index 62fb6f1..29f596a 100644
--- a/README.md
+++ b/README.md
@@ -18,7 +18,6 @@
   <a href="https://pub.dev/packages/meilisearch"><img src="https://img.shields.io/pub/v/meilisearch" alt="Pub Version"></a>
   <a href="https://github.com/meilisearch/meilisearch-dart/actions"><img src="https://github.com/meilisearch/meilisearch-dart/workflows/Tests/badge.svg" alt="GitHub Workflow Status"></a>
   <a href="https://github.com/meilisearch/meilisearch-dart/blob/main/LICENSE"><img src="https://img.shields.io/badge/license-MIT-informational" alt="License"></a>
-  <a href="https://ms-bors.herokuapp.com/repositories/66"><img src="https://bors.tech/images/badge_small.svg" alt="Bors enabled"></a>
   <a href="https://codecov.io/gh/meilisearch/meilisearch-dart"><img src="https://codecov.io/gh/meilisearch/meilisearch-dart/branch/main/graph/badge.svg" alt="Code Coverage"></a>
 </p>
 
@@ -200,10 +199,10 @@ The `MeiliDocumentContainer<T>` class contains meilisearch-specific fields (e.g.
 We define the `mapToContainer()` extension to help you quickly opt-in to this class, example:
 
 ```dart
-final res = await index 
-      .search("hello world") 
+final res = await index
+      .search("hello world")
       .asSearchResult() //or .asPaginatedResult() if using page parameters
-      .mapToContainer(); 
+      .mapToContainer();
 ```
 
 ## 🤖 Compatibility with Meilisearch