You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+5-24Lines changed: 5 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,23 +2,12 @@
2
2
3
3
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.
4
4
5
-
-[Hacktoberfest](#hacktoberfest)
6
5
-[Assumptions](#assumptions)
7
6
-[How to Contribute](#how-to-contribute)
8
7
-[Development Workflow](#development-workflow)
9
8
-[Git Guidelines](#git-guidelines)
10
9
-[Release Process (for internal team only)](#release-process-for-internal-team-only)
🚀 If your PR gets accepted it will count into your participation to Hacktoberfest!
17
-
18
-
✅ To be accepted it has either to have been merged, approved or tagged with the `hacktoberfest-accepted` label.
19
-
20
-
🧐 Don't forget to check the [quality standards](https://hacktoberfest.digitalocean.com/resources/qualitystandards)! Low-quality PRs might get marked as `spam` or `invalid`, and will not count toward your participation in Hacktoberfest.
21
-
22
11
## Assumptions
23
12
24
13
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.**
@@ -91,14 +80,6 @@ yarn playground:html
91
80
92
81
A playground is available to try out the [GeoSearch](./README.md/-geo-search) in `instant-meilisearch`.
93
82
94
-
Unfortunately, for the moment, no online dataset is provided. Meaning that to make the playground work, you will have to set up your MeiliSearch accordingly to the playground needs.
95
-
96
-
To do so follow these steps:
97
-
98
-
1. Run a MeiliSeaerch instance. See [Setup](#setup) section to launch MeiliSearch with `Docker`. It is important to use the same `host` and `apikey` as provided in the `setup` section.
99
-
2. Add the settings and the documents to your running MeiliSearch instance. We provide a script that does this automatically. Please run `node playgrounds/geo-javascript/setup/index.js`. Or you can look at the script to take inspiration!
100
-
4. Run the playground!
101
-
102
83
```bash
103
84
yarn playground:geo-javascript
104
85
```
@@ -128,7 +109,7 @@ Some notes on GitHub PRs:
128
109
129
110
-[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>
130
111
The draft PR can be very useful if you want to show that you are working on something and make your work visible.
131
-
- 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/guides/bors.md) to automatically enforce this requirement without the PR author having to do it manually.
112
+
- 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.
132
113
- All PRs must be reviewed and approved by at least one maintainer.
133
114
- 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/instant-meilisearch/releases/).
### Automation to Rebase and Merge the PRs <!-- omit in TOC -->
140
121
141
122
This project integrates a bot that helps us manage pull requests merging.<br>
142
-
_[Read more about this](https://github.com/meilisearch/integration-guides/blob/main/guides/bors.md)._
123
+
_[Read more about this](https://github.com/meilisearch/integration-guides/blob/main/resources/bors.md)._
143
124
144
125
### Automated Changelogs <!-- omit in TOC -->
145
126
146
127
This project integrates a tool to create automated changelogs.<br>
147
-
_[Read more about this](https://github.com/meilisearch/integration-guides/blob/main/guides/release-drafter.md)._
128
+
_[Read more about this](https://github.com/meilisearch/integration-guides/blob/main/resources/release-drafter.md)._
148
129
149
130
### How to Publish the Release <!-- omit in TOC -->
150
131
151
-
⚠️ Before doing anything, make sure you got through the guide about [Releasing an Integration](https://github.com/meilisearch/integration-guides/blob/main/guides/integration-release.md).
132
+
⚠️ Before doing anything, make sure you got through the guide about [Releasing an Integration](https://github.com/meilisearch/integration-guides/blob/main/resources/integration-release.md).
152
133
153
134
Make a PR modifying the file [`package.json`](/package.json) with the right version.
154
135
155
136
```javascript
156
137
"version":"X.X.X"
157
138
```
158
139
159
-
Once the changes are merged on `main`, you can publish the current draft release via the [GitHub interface](https://github.com/meilisearch/instant-meilisearch/releases).
140
+
Once the changes are merged on `main`, you can publish the current draft release via the [GitHub interface](https://github.com/meilisearch/instant-meilisearch/releases): on this page, click on `Edit` (related to the draft release) > update the description (be sure you apply [these recommandations](https://github.com/meilisearch/integration-guides/blob/main/resources/integration-release.md#writting-the-release-description)) > when you are ready, click on `Publish release`.
160
141
161
142
GitHub Actions will be triggered and push the package to [npm](https://www.npmjs.com/package/@meilisearch/instant-meilisearch).
Copy file name to clipboardExpand all lines: playgrounds/geo-javascript/README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
1
# Javascript GeoSearch Playground
2
2
3
-
To run this playground you will first have to set up your MeiliSearch accordingly to the playground needs. To do so please follow the steps in our [contributing guide](./CONTRIBUTING.md#-geo-search-playground).
3
+
The provided Google Maps API Key is limited to 300 requests per day, so it might be down sometimes. In which case, please create a new [Google API Key](https://developers.google.com/maps/documentation/javascript/get-api-key) and add it in the `.env` file at the root of the playground: `/playgrounds/geo-javascript`.
4
4
5
-
The provided Google Maps Api Key is limited at 300 requests per day, so it might be down sometimes. In which case, please create a new [Google Api Key](https://developers.google.com/maps/documentation/javascript/get-api-key) and add it in the `.env` file at the root of the playground: `/playgrounds/geo-javascript`
5
+
The same dataset is [downloadable here](https://github.com/meilisearch/datasets/tree/main/datasets/world_cities) if you want to try it out on your own MeiliSearch.
0 commit comments