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
🚀 If your PR gets accepted it will count into your participation to Hacktoberfest!
21
-
22
-
✅ To be accepted it has either to have been merged, approved or tagged with the `hacktoberfest-accepted` label.
23
-
24
-
🧐 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.
25
-
26
15
## Assumptions
27
16
28
17
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.**
@@ -151,7 +140,7 @@ Some notes on GitHub PRs:
151
140
152
141
-[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>
153
142
The draft PR can be very useful if you want to show that you are working on something and make your work visible.
154
-
- 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.
143
+
- 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.
155
144
- All PRs must be reviewed and approved by at least one maintainer.
156
145
- 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-ruby/releases/).
### Automation to Rebase and Merge the PRs <!-- omit in toc -->
163
152
164
153
This project integrates a bot that helps us manage pull requests merging.<br>
165
-
_[Read more about this](https://github.com/meilisearch/integration-guides/blob/main/guides/bors.md)._
154
+
_[Read more about this](https://github.com/meilisearch/integration-guides/blob/main/resources/bors.md)._
166
155
167
156
### Automated Changelogs <!-- omit in toc -->
168
157
169
158
This project integrates a tool to create automated changelogs.<br>
170
-
_[Read more about this](https://github.com/meilisearch/integration-guides/blob/main/guides/release-drafter.md)._
159
+
_[Read more about this](https://github.com/meilisearch/integration-guides/blob/main/resources/release-drafter.md)._
171
160
172
161
### How to Publish the Release <!-- omit in toc -->
173
162
174
-
⚠️ 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).
163
+
⚠️ 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).
175
164
176
165
Make a PR modifying the file [`lib/meilisearch/version.rb`](/lib/meilisearch/version.rb) with the right version.
177
166
178
167
```ruby
179
168
VERSION='X.X.X'
180
169
```
181
170
182
-
Once the changes are merged on `main`, you can publish the current draft release via the [GitHub interface](https://github.com/meilisearch/meilisearch-ruby/releases).
171
+
Once the changes are merged on `main`, you can publish the current draft release via the [GitHub interface](https://github.com/meilisearch/meilisearch-ruby/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`.
183
172
184
173
GitHub Actions will be triggered and push the package to [RubyGems](https://rubygems.org/gems/meilisearch).
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -198,7 +198,7 @@ JSON output:
198
198
199
199
## 🤖 Compatibility with MeiliSearch
200
200
201
-
This package only guarantees the compatibility with the [version v0.23.0 of MeiliSearch](https://github.com/meilisearch/MeiliSearch/releases/tag/v0.23.0).
201
+
This package only guarantees the compatibility with the [version v0.24.0 of MeiliSearch](https://github.com/meilisearch/MeiliSearch/releases/tag/v0.24.0).
0 commit comments