diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-12-07 00:10:14 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-12-07 00:10:14 +0300 |
| commit | 36c5bf80d4aaedba332a420e3d620b2ee9e2bb65 (patch) | |
| tree | 1a680ddbedf2dfc183b655e2c944a31b54b7fd6f /doc/user/search/advanced_search.md | |
| parent | a15c9bc9eb04dcee1369c5fd6248c6352915ad21 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/user/search/advanced_search.md')
| -rw-r--r-- | doc/user/search/advanced_search.md | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/user/search/advanced_search.md b/doc/user/search/advanced_search.md index 20881a6bdb3..f0a3543f6af 100644 --- a/doc/user/search/advanced_search.md +++ b/doc/user/search/advanced_search.md @@ -52,13 +52,13 @@ The Advanced Search can be useful in various scenarios: ## Use the Advanced Search syntax -Elasticsearch has only data for the default branch. That means that if you go +Elasticsearch has data for the default branch only. That means that if you go to the repository tree and switch the branch from the default to something else, -then the "Code" tab in the search result page will be served by the basic +then the **Code** tab in the search result page is served by the basic search even if Elasticsearch is enabled. The Advanced Search syntax supports fuzzy or exact search queries with prefixes, -boolean operators, and much more. Use the search as before and GitLab will show +boolean operators, and much more. Use the search as before and GitLab shows you matching code from each project you have access to.  @@ -67,7 +67,7 @@ Full details can be found in the [Elasticsearch documentation](https://www.elast here's a quick guide: - Searches look for all the words in a query, in any order - for example: searching - issues for [`display bug`](https://gitlab.com/search?snippets=&scope=issues&repository_ref=&search=display+bug&group_id=9970&project_id=278964) and [`bug display`](https://gitlab.com/search?snippets=&scope=issues&repository_ref=&search=bug+Display&group_id=9970&project_id=278964) will return the same results. + issues for [`display bug`](https://gitlab.com/search?snippets=&scope=issues&repository_ref=&search=display+bug&group_id=9970&project_id=278964) and [`bug display`](https://gitlab.com/search?snippets=&scope=issues&repository_ref=&search=bug+Display&group_id=9970&project_id=278964) return the same results. - To find the exact phrase (stemming still applies), use double quotes: [`"display bug"`](https://gitlab.com/search?snippets=&scope=issues&repository_ref=&search=%22display+bug%22&group_id=9970&project_id=278964) - To find bugs not mentioning display, use `-`: [`bug -display`](https://gitlab.com/search?snippets=&scope=issues&repository_ref=&search=bug+-display&group_id=9970&project_id=278964) - To find a bug in display or banner, use `|`: [`bug display | banner`](https://gitlab.com/search?snippets=&scope=issues&repository_ref=&search=bug+display+%7C+banner&group_id=9970&project_id=278964) @@ -85,7 +85,7 @@ Advanced Search also supports the use of filters. The available filters are: - `blob`: Filters by Git `object ID`. Exact match only. To use them, add them to your keyword in the format `<filter_name>:<value>` without -any spaces between the colon (`:`) and the value. When no keyword is provided, an asterisk (`*`) will be used as the keyword. +any spaces between the colon (`:`) and the value. When no keyword is provided, an asterisk (`*`) is used as the keyword. Examples: |