Migrate CI from bors to merge queue

.github/workflows/tests.yml

@@ -2,13 +2,10 @@ name: Tests
 
 on:
   pull_request:
+  merge_group:
   push:
-    # trying and staging branches are for BORS config
     branches:
-      - trying
-      - staging
       - main
-      - feature/**
       - v1.x
 
 jobs:

CONTRIBUTING.md

@@ -1,6 +1,6 @@
 # Contributing
 
-First of all, thank you for contributing to Meilisearch! The goal of this document is to provide everything you need to know in order to contribute to Meilisearch and its different integrations.
+Thank you for considering contributing to Meilisearch! This document provides everything you need to know in order to contribute to Meilisearch PHP.
 
 <!-- MarkdownTOC autolink="true" style="ordered" indent="   " -->
 
@@ -14,9 +14,9 @@ First of all, thank you for contributing to Meilisearch! The goal of this docume
 
 ## Assumptions
 
-1. **You're familiar with [GitHub](https://github.com) and the [Pull Request](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/about-pull-requests) (PR) workflow.**
-2. **You've read the Meilisearch [documentation](https://docs.meilisearch.com) and the [README](/README.md).**
-3. **You know about the [Meilisearch community](https://discord.meilisearch.com). Please use this for help.**
+1. **You're familiar with [GitHub](https://github.com) and [Pull Requests](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/about-pull-requests).**
+2. **You've read the Meilisearch [documentation](https://docs.meilisearch.com) and this SDK's [README](/README.md).**
+3. **You know about the [Meilisearch community](https://dub.sh/meili-discord?utm_campaign=oss&utm_source=github). Please use this for help.**
 
 ## How to Contribute
 
@@ -25,8 +25,9 @@ First of all, thank you for contributing to Meilisearch! The goal of this docume
 3. [Create a new Git branch](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository).
 4. Review the [Development Workflow](#development-workflow) section that describes the steps to maintain the repository.
 5. Make the changes on your branch.
-6. [Submit the branch as a PR](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork) pointing to the `main` branch of the main meilisearch-php repository. A maintainer should comment and/or review your Pull Request within a few days. Although depending on the circumstances, it may take longer.<br>
- We do not enforce a naming convention for the PRs, but **please use something descriptive of your changes**, having in mind that the title of your PR will be automatically added to the next [release changelog](https://github.com/meilisearch/meilisearch-php/releases/).
+6. [Submit the branch as a PR](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork) pointing to the `main` branch of the main meilisearch-php repository.
+
+Read more about [Git guidelines](#git-guidelines) below.
 
 ## Development Workflow
 
@@ -82,23 +83,17 @@ 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.
+- The branch related to the PR must be **up-to-date with `main`** before merging. This project uses [Merge Queues](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue) to automatically enforce this requirement.
 - 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-php/releases/).
 
 ## Release Process (for the internal team only)
 
 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.<br>
-_[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.<br>
-_[Read more about this](https://github.com/meilisearch/integration-guides/blob/main/resources/release-drafter.md)._
+This project uses [Release Drafter](https://github.com/release-drafter/release-drafter) to automate changelog creation.
 
 ### How to Publish the Release
 
@@ -120,4 +115,4 @@ A WebHook will be triggered and push the package to [Packagist](https://packagis
 
 <hr>
 
-Thank you again for reading this through. We can not wait to begin to work with you if you make your way through this contributing guide ❤️
+Thank you for reading this through ❤️ We're excited to collaborate with you!