Bors (#161)

* Add Bors config

* Update CONTRIBUTING.md

Author: curquiza

.github/workflows/test.yml

@@ -1,13 +1,17 @@
-name: Pytest
+name: Tests
 
 on:
+  pull_request:
   push:
+    # trying and staging branches are for BORS config
     branches:
+      - trying
+      - staging
       - master
-  pull_request:
 
 jobs:
-  build:
+  test:
+    name: python-tests
     runs-on: ubuntu-latest
 
     steps:

CONTRIBUTING.md

@@ -114,7 +114,7 @@ We don't follow any other convention, but if you want to use one, we recommend [
 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 `master`** before merging. You need to [rebase your branch](https://gist.github.com/curquiza/5f7ce615f85331f083cd467fc4e19398) if it is not.
+- The branch related to the PR must be **up-to-date with `master`** before merging. [Bors](https://github.com/bors-ng/bors-ng) will rebase your branch if it is not. Ask a maintainer to run it.
 - All PRs must be reviewed and approved by at least one maintainer.
 - All PRs have to be **squashed and merged**.
 - 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 changlogs](https://github.com/meilisearch/meilisearch-python/releases/).

bors.toml

@@ -0,0 +1,3 @@
+status = ["python-tests"]
+# 1 hour timeout
+timeout-sec = 3600