Skip to content

Commit 76bdcdf

Browse files
authored
docs: update third-party service reference from Elasticsearch to Meilisearch in Tutor Main instructions (#1258)
1 parent ffe2017 commit 76bdcdf

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/tutorials/main.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@ When running Tutor Main, you usually do not want to override your existing Tutor
5858
Making changes to Tutor Main
5959
----------------------------
6060

61-
In general pull requests should be open on the "release" branch of Tutor: the "release" branch is automatically merged on the "main" branch at every commit, such that changes made to Tutor releases find their way to Tutor Main as soon as they are merged. However, sometimes you want to make changes to Tutor Main exclusively, and not to the Tutor releases. This might be the case for instance when upgrading the running version of a third-party service (for instance: Elasticsearch, MySQL), or when the release branch requires specific changes. In that case, you should follow the instructions from the :ref:`contributing` section of the docs, with the following differences:
61+
In general pull requests should be open on the "release" branch of Tutor: the "release" branch is automatically merged on the "main" branch at every commit, such that changes made to Tutor releases find their way to Tutor Main as soon as they are merged. However, sometimes you want to make changes to Tutor Main exclusively, and not to the Tutor releases. This might be the case for instance when upgrading the running version of a third-party service (for instance: Meilisearch, MySQL), or when the release branch requires specific changes. In that case, you should follow the instructions from the :ref:`contributing` section of the docs, with the following differences:
6262

6363
- Open your pull request on top of the "main" branch instead of "release".
6464
- Add a description of your changes by creating a changelog entry with `make changelog-entry`, as in the release branch.

0 commit comments

Comments
 (0)