Welcome to mirror list, hosted at ThFree Co, Russian Federation.

exact_code_search.md « search « user « doc - gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
blob: f35548043977c92a2fe813d77740a724e2c05ada (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
---
stage: Data Stores
group: Global Search
info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments"
---

# Exact Code Search **(PREMIUM ALL)**

> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/105049) in GitLab 15.9 [with a flag](../../administration/feature_flags.md) named `index_code_with_zoekt` for indexing and `search_code_with_zoekt` for searching. Both are disabled by default.

WARNING:
We are still actively making changes to the Exact Code Search feature. GitLab will dogfood it first, and roll it out only to specific customers on GitLab.com who request access to it. We will make an announcement when it's available for GitLab.com customers to tryout. You can follow our development progress by checking [the Exact Code Search feature roadmap](https://gitlab.com/groups/gitlab-org/-/epics/9404).
On self-managed GitLab, it is technically possible to enable this feature, however, GitLab does not provide support or documentation at this stage of development and it has not been widely tested at scale. There are also many known limitations.

## Usage

When performing any Code search in GitLab it will choose to use "Exact Code
Search" powered by [Zoekt](https://github.com/sourcegraph/zoekt) if the project
is part of an enabled Group.

The main differences between Zoekt and [advanced search](advanced_search.md)
are that Zoekt provides exact substring matching as well as allows you to
search for regular expressions. Since it allows searching for regular
expressions, certain special characters will require escaping. Backslash can
escape special characters and wrapping in double quotes can be used for phrase
searches.

## Syntax

This table shows some example queries for exact code search.

| Query                | Description                                                                           |
| -------------------- |-------------------------------------------------------------------------------------- |
| `foo`                | Returns files that contain `foo`                                                      |
| `foo file:^doc/`     | Returns files that contain `foo` in directories that start with `doc/`                |
| `"class foo"`        | Returns files that contain the exact string `class foo`                               |
| `class foo`          | Returns files that contain both `class` and `foo`                                     |
| `foo or bar`         | Returns files that contain either `foo` or `bar`                                      |
| `class Foo`          | Returns files that contain `class` (case insensitive) and `Foo` (case sensitive)      |
| `class Foo case:yes` | Returns files that contain `class` and `Foo` (both case sensitive)                    |
| `foo -bar`           | Returns files that contain `foo` but not `bar`                                        |
| `foo file:js`        | Searches for `foo` in files with names that contain `js`                              |
| `foo -file:test`     | Searches for `foo` in files with names that do not contain `test`                     |
| `foo lang:ruby`      | Searches for `foo` in Ruby source code                                                |
| `foo file:\.js$`     | Searches for `foo` in files with names that end with `.js`                            |
| `foo.*bar`           | Searches for strings that match the regular expression `foo.*bar`                     |