Skip to content

Collections

Collections organize evidence and entities for an investigation. A collection can contain code-search matches, workspace results, repositories, and GitHub accounts. Use it to keep related items together and restrict a new search to their repository scope.

Collections belong to your account. They are separate from a saved query and from the Saved view in workspace Results.

  1. Open Collections in the application sidebar.
  2. Select New collection.
  3. Enter a name of up to 100 characters, then select Create collection.
  4. Open Add entities to add repositories or accounts.

Choose Repositories and enter identifiers such as owner/project, or choose GitHub accounts and enter account names. Enter one identifier per line, up to 100 per batch. Select Add to collection to finish. Items already present are reported rather than added again.

Adding an identifier organizes your investigation; it does not request a new crawl or guarantee that the repository has indexed files.

Collect search matches and workspace results

Section titled “Collect search matches and workspace results”

In Search, open a row’s More actions menu and choose Add to collection. Choose an existing collection and confirm Add, or enter a new collection name and select Create & add.

Choose Collect repository instead when you want the repository as an entity without collecting that individual match. Workspace Results provides the same row actions and an Add to collection action for selected rows.

Code-search matches need a current search receipt to be added. If adding an older match fails with a request to search again, rerun the query and collect the new match. A collected preview is not a full-file archive.

Save and Add to collection serve different purposes: Save marks evidence in workspace Results; Add to collection groups an item with the entities in your investigation.

Open a collection to switch between Graph and Entities.

The graph connects results to their repositories and accounts to matching repository namespaces. These links do not prove that an account contributed to a repository or owns an organization. Unconnected entities remain separate.

Drag nodes to arrange them, zoom or reset the view, and use Pause motion when helpful. Keyboard users can focus a node, move it with arrow keys, and select it with Enter. The graph shows up to 200 nodes; use Entities to browse the rest.

Entities displays up to 50 items per page. Select an entity to inspect its available details. Use Previous page and Next page to continue browsing.

  1. Open the collection and select Search collection.
  2. Confirm that Search shows Searching collection and the intended name.
  3. Enter a literal query or enable Use regex, then run the search.

The scope includes explicitly collected repositories, repositories referenced by collected results, and repositories within collected GitHub account namespaces. These are alternatives within the collection scope. Search still examines the available indexed snapshots; it does not search only the saved preview text or fetch every repository live.

Collection search accepts at most 200 distinct account and repository scope entries. Narrow the collection if that limit is reached. An empty collection returns no matches. An unavailable collection produces an error rather than silently searching all code.

Select Search all code to leave the collection scope. This broader query is a separate search and uses the normal account allowance. Table filters still narrow only the matches already received.

Saved searches store the query and regex mode, not the collection scope. When returning to a scoped investigation, open Search collection again and confirm the collection banner before running a query.

In Entities, select rows and choose Remove selected. Confirm Remove from collection. Select all applies to the current page only.

Removing membership preserves the source results and repositories. A collection can hold up to 5,000 entities; remove unneeded members or organize a larger investigation into separate collections.

Collections are available in the browser application. The customer API does not support collection management or collection-scoped search.