Skip to content

Commit 9acdfa9

Browse files
authored
Update CONTRIBUTING.md
1 parent 7fe16d1 commit 9acdfa9

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

CONTRIBUTING.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ First of all, thank you for contributing to MeiliSearch! The goal of this docume
2424
3. [Create a new Git branch](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository).
2525
4. Review the [Development Workflow](#workflow) section that describes the steps to maintain the repository.
2626
5. Make your changes.
27-
6. [Submit the branch as a PR](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork) pointing to the `master` branch of the main meilisearch-ruby reposotory. A maintainer should comment and/or review your Pull Request within a few days. Although depending on the circumstances, it may take longer.<br>
27+
6. [Submit the branch as a PR](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork) pointing to the `master` branch of the main meilisearch-ruby repository. A maintainer should comment and/or review your Pull Request within a few days. Although depending on the circumstances, it may take longer.<br>
2828
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](https://github.com/meilisearch/meilisearch-ruby/releases/).
2929

3030
## Development Workflow
@@ -137,7 +137,7 @@ We do not enforce any branch naming style, but please use something descriptive
137137
As minimal requirements, your commit message should:
138138
- be capitalized
139139
- not finish by a dot or any other punctuation character (!,?)
140-
- start with a verb so that we can read your commit message this way: "This commmit will ...", where "..." is the commit message.
140+
- start with a verb so that we can read your commit message this way: "This commit will ...", where "..." is the commit message.
141141
e.g.: "Fix the home page button" or "Add more tests for create_index method"
142142

143143
We don't follow any other convention, but if you want to use one, we recommend [this one](https://chris.beams.io/posts/git-commit/).

0 commit comments

Comments
 (0)