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!
17
17
18
-
✅ To be accepted it has either to have been merged, approved or tagged with the `hacktoberest-accepted` label.
18
+
✅ To be accepted it has either to have been merged, approved or tagged with the `hacktoberfest-accepted` label.
19
19
20
-
🧐 Don't forget to check the [quality standards](https://hacktoberfest.digitalocean.com/resources/qualitystandards), otherwise your PR could be marked as `spam` or `invalid`, and it will not be counted toward your participation in Hacktoberfest.
20
+
🧐 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.
1. Make sure that the contribution you want to make is explained or detailed in a GitHub issue! Find an [existing issue](https://github.com/meilisearch/meilisearch-kubernetes/issues/) or [open a new one](https://github.com/meilisearch/meilisearch-kubernetes/issues/new).
31
31
2. Once done, [fork the meilisearch-kubernetes repository](https://help.github.com/en/github/getting-started-with-github/fork-a-repo) in your own GitHub account. Ask a maintainer if you want your issue to be checked before making a PR.
32
32
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).
33
-
4. Review the [Development Workflow](#workflow) section that describes the steps to maintain the repository.
33
+
4. Review the [Development Workflow](#development-workflow) section that describes the steps to maintain the repository.
34
34
5. Make the changes on your branch.
35
35
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 `main` branch of the main meilisearch-kubernetes 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>
36
36
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-kubernetes/releases/).
0 commit comments