From 9000cf59dd84bf42ff3c3a6ead2aa4d9ca6ac29e Mon Sep 17 00:00:00 2001
From: curquiza
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/strapi-plugin-meilisearch/releases/).
@@ -117,11 +116,6 @@ Some notes on GitHub PRs:
Meilisearch tools follow the [Semantic Versioning Convention](https://semver.org/).
-### Automation to Rebase and Merge the PRs
-
-This project integrates a bot that helps us manage pull requests merging.
-_[Read more about this](https://github.com/meilisearch/integration-guides/blob/main/resources/bors.md)._
-
### Automated Changelogs
This project integrates a tool to create automated changelogs.
diff --git a/README.md b/README.md
index 3c7958af..1bcd2988 100644
--- a/README.md
+++ b/README.md
@@ -19,7 +19,6 @@
-
âš¡ The Meilisearch plugin for Strapi