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.**
-[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>
97
86
The draft PR can be very useful if you want to show that you are working on something and make your work visible.
98
-
- 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.
87
+
- 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.
99
88
- All PRs must be reviewed and approved by at least one maintainer.
100
89
- 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-js/releases/).
This project integrates a bot that helps us manage pull requests merging.<br>
109
-
_[Read more about this](https://github.com/meilisearch/integration-guides/blob/main/guides/bors.md)._
98
+
_[Read more about this](https://github.com/meilisearch/integration-guides/blob/main/resources/bors.md)._
110
99
111
100
### Automated Changelogs
112
101
113
102
This project integrates a tool to create automated changelogs.<br>
114
-
_[Read more about this](https://github.com/meilisearch/integration-guides/blob/main/guides/release-drafter.md)._
103
+
_[Read more about this](https://github.com/meilisearch/integration-guides/blob/main/resources/release-drafter.md)._
115
104
116
105
### How to Publish the Release
117
106
118
-
⚠️ 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).
107
+
⚠️ 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).
119
108
120
109
Make a PR modifying the file [`package.json`](/package.json) with the right version.
121
110
122
111
```javascript
123
112
"version":"X.X.X",
124
113
```
125
114
126
-
Once the changes are merged on `main`, you can publish the current draft release via the [GitHub interface](https://github.com/meilisearch/meilisearch-js/releases).
115
+
Once the changes are merged on `main`, you can publish the current draft release via the [GitHub interface](https://github.com/meilisearch/meilisearch-js/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`.
127
116
128
117
GitHub Actions will be triggered and push the package to [npm](https://www.npmjs.com/package/meilisearch).
0 commit comments