- Searching across different releases
- Searching through feature branches during development
- Tracking changes across multiple maintenance branches simultaneously
Configuration
Multi-branch indexing is configured in the connection using therevisions.branches and revisions.tags arrays. Glob patterns are supported. For example:
branches and tags array will be indexed.
Per-repository overrides
Userevisions.overrides to index different branches or tags for specific repos in a connection. For example, you can index datastore-release/* branches only for the acme/datastore repo:
The
mode controls how the override combines with the connection-level branches and tags:
appendindexes the connection-level patterns and the override’s patterns.replaceindexes only the override’s patterns. If you omitbranchesortagsfrom the override, the connection-level value is used for that field.
repospatterns match the repo’s display name (e.g.,acme/datastore) or its full name (e.g.,github.com/acme/datastore).- Matching is case-insensitive.
- If more than one override matches a repo, only the first one is applied.
- The 64 revision limit applies after overrides are resolved. Use
replaceto narrow the revisions for repos with many matching branches.
Search syntax
To search branches other than the default, therev: prefix can be used followed by the branch (or tag) name:
To search across all branches,
rev:*:
Additional info:
refs/heads/orrefs/tags/can be included to fully qualify a branch or a tag, respectively. E.g.,rev:refs/heads/foowill search the branchfoo, whilerev:refs/tags/foowill search the tagfoo.rev:does not support regular expressions or glob patterns. It uses a simplecontainscall between the branch name and the pattern. See here.

