Skip to content

Latest commit

 

History

History
173 lines (113 loc) · 7.61 KB

CONTRIBUTING.md

File metadata and controls

173 lines (113 loc) · 7.61 KB

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 meilisearch-rust 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 meilisearch-rust 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

Tests

All the tests are documentation tests.
Since they are all making operations on the MeiliSearch server, running all the tests simultaneously would cause panics.

To run the tests one by one, run:

# Tests
curl -L https://install.meilisearch.com | sh # download MeiliSearch
./meilisearch --master-key=masterKey --no-analytics=true # run MeiliSearch
cargo test -- --test-threads=1

Also, the WASM example compilation should be checked:

rustup target add wasm32-unknown-unknown
cargo check --example web_app --target wasm32-unknown-unknown --features=sync

Each PR should pass the tests to be accepted.

Clippy

Each PR should pass clippy (the linter) to be accepted.

cargo clippy -- -D warnings

If you don't have clippy installed on your machine yet, run:

rustup update
rustup component add clippy

⚠️ Also, if you have installed clippy a long time ago, you might need to update it:

rustup update

Update the README

The README is generated. Please do not update manually the README.md file.

Instead, update the README.tpl and src/lib.rs files, and run:

sh scripts/update-readme.sh

Then, push the changed files.

You can check the current README.md is up-to-date by running:

sh scripts/check-readme.sh
# To see the diff
sh scripts/check-readme.sh --diff

If it's not, the CI will fail on your PR.

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 file Cargo.toml:

version = "X.X.X"

and the README.tpl:

//! meilisearch-sdk = "X.X.X"

with the right version.

You should run the following command after the changes applied to lib.rs:

sh scripts/update-readme.sh

Also, you might need to change the code-samples file if the minor has been upgraded:

  meilisearch-sdk = "X.X"

Once the changes are merged on main, you can publish the current draft release via the GitHub interface: on this page, click on Edit (related to the draft release) > update the description (be sure you apply these recommandations) > when you are ready, click on Publish release.

GitHub Actions will be triggered and push the package to crates.io.

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 ❤️