Search syntax
Codeup provides enterprise-level code search across multiple repositories. This topic describes the search syntax you can use to find code efficiently and accurately.
Keywords
Keyword | Description | Example |
repo | Searches by repository path or name. | repo:myrepo searches for repositories where the path or name contains "myrepo". Wildcard characters, such as my*, are supported. |
mine | Specifies whether a user is a member of the code repository. Valid values are true and false. | mine:true searches for repositories where you are a member. |
file | Searches by file path. | The path file:/home/admin/logs supports wildcard characters. |
ext | Searches by file name extension, such as txt or md. | ext:txt searches for files with the txt extension. |
lang | Searches by programming language, such as Java or C. | Use lang:Java to search for Java code repositories. |
author | To specify the author of a commit or the creator of a merge request, you must use an organization member's name or a nickname from your personal settings. | author:misha specifies that misha is the author of the commit or merge request. |
reviewer | To specify a reviewer for a merge request, you must use the name of an organization member or a nickname from personal settings. | reviewer:misha is a query for merge requests reviewed by misha. |
mrstate | Searches by merge request status. The supported values are merged, closed, opened, and accepted. | mrstate:opened finds open merge requests. |
visibility | Specify whether the code repository is | visibility:private finds private repositories within the organization. |
Connectors | Description |
AND | Finds results where both terms exist. If you do not specify an operator, AND is used by default. |
OR | Logical OR. |
NOT | Excludes results that contain the term. You can also use a hyphen (-) as a substitute. For example, -repo:myrepo excludes the myrepo repository from the search. |