Skip to content

Latest commit

 

History

History
133 lines (86 loc) · 7.62 KB

CONTRIBUTING.md

File metadata and controls

133 lines (86 loc) · 7.62 KB
Raw

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.

Assumptions

  1. You're familiar with GitHub and the Pull Request(PR) workflow.
  2. You've read the Meilisearch documentation and the README.
  3. You know about the Meilisearch community. Please use this for help.

How to Contribute

  1. Make sure that the contribution you want to make is explained or detailed in a GitHub issue! Find an existing issue or open a new one.
  2. Once done, fork the mini-dashboard repository in your own GitHub account. Ask a maintainer if you want your issue to be checked before making a PR.
  3. Create a new Git branch.
  4. Review the 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 pointing to the main branch of the main mini-dashboard repository. A maintainer should comment and/or review your Pull Request within a few days. Although depending on the circumstances, it may take longer.
    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.

Development Workflow

Setup 

yarn

Tests and Linter

Each PR should pass the linter to be accepted.

yarn lint

Storybook

This project's components are in Storybook. If you edit one of the components, please make sure that storybook is still up-to-date.

yarn storybook

Git Guidelines

Git Branches

All changes must be made in a branch and submitted as PR. We do not enforce any branch naming style, but please use something descriptive of your changes.

Git Commits

As minimal requirements, your commit message should:

  • be capitalized
  • not finish by a dot or any other punctuation character (!,?)
  • start with a verb so that we can read your commit message this way: "This commit will ...", where "..." is the commit message. e.g.: "Fix the home page button" or "Add more tests for create_index method"

We don't follow any other convention, but if you want to use one, we recommend this one.

GitHub Pull Requests

Some notes on GitHub PRs:

  • Convert your PR as a draft if your changes are a work in progress: no one will review it until you pass your PR as ready for review.
    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 to automatically enforce this requirement without the PR author having to do it manually.
  • 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.

Release Process (for internal team only)

Meilisearch tools follow the Semantic Versioning Convention.

Automation to Rebase and Merge the PRs

This project integrates a bot that helps us manage pull requests merging.
Read more about this.

Automated Changelogs

This project integrates a tool to create automated changelogs.
Read more about this.

How to Publish the Release

⚠️ Before doing anything, make sure you got through the guide about Releasing an Integration.

Make a PR modifying the following files with the right version:

package.json:

"version": "X.X.X",

src/version/version.js

export default 'X.X.X'

Once the changes are merged on main, you can publish the current draft release via the GitHub interface.

GitHub Actions will be triggered and generate a build used by the Meilisearch engine

Add to Meilisearch Engine

The mini-dashboard is part of the Meilisearch engine's binary. In order for the engine to be built with the mini-dashboard, these are the steps to follow:

  • Publish the mini-dashboard.
  • Ask to the engine-team on which branch the mini-dashboard should be updated.
  • Create a new branch pointing to that branch.
  • Update the /meilisearch/Cargo.toml file with the link to the latest build.zip of the mini-dashboard (see example). The link can be found in the assets section of the latest release of the mini-dashboard (see example). Copy the link of the build.zip by right-clicking and selecting copy link address.
  • Update the sha of the build.zip in /meilisearch/Cargo.toml. To get the shasum of the file, download the build.zip and find its shasum.
  • Make a PR on meilisearch, with the changes pointing to the required branch (see step 2).

During a pre-release of meilisearch, an additional step is required before publishing the mini-dashboard:

  • If there are breaking changes on the search, update the version of meilisearch-js and instant-meilisearch to their latest compatible version with the pre-release. It may be a beta or the latest release. Check with the integration-team to know if it is required or not.

Thank you again for reading this through, we can not wait to begin to work with you if you made your way through this contributing guide ❤️