Results & saved evidence
Results brings together captured code-search matches and findings from monitoring. The current sidebar entry is Saved results; the page provides All results, Saved, and Ignored views.
Review a result
Section titled “Review a result”- Open Saved results in the workspace sidebar.
- Choose the view you need.
- Select a filename or match preview to open Result details.
- Review the repository, matched text, context, and available metadata.
- Use Open on GitHub when a source URL is available.
The drawer supports previous and next navigation, copying the available context, and expanding it for easier reading.
Saved search matches contain a snapshot reference and excerpt. Monitoring results can contain an added line or commit-diff excerpt. The drawer’s File content label does not guarantee a complete file.
Understand result origin
Section titled “Understand result origin”| Label | Origin |
|---|---|
| Saved from search | A match explicitly captured from Search |
| Live monitoring | A result identified by its monitoring source metadata |
| Workspace result | A result without one of those explicit source labels |
Use the commit reference and rule-related signals when available to understand a result’s context. A generic source label does not by itself establish how a record was collected.
Save, ignore, and restore
Section titled “Save, ignore, and restore”Save result keeps an unreviewed result in the Saved view. Search matches captured with Save are saved immediately. A Saved button indicates that the result is already saved.
Ignore result moves an unreviewed result out of the review flow. Open Ignored and use Restore result to bring an ignored result back for review.
Use row selection for Save selected or Ignore selected when those controls are available. Bulk Ignore removes the selected items from Saved as well, so check the selection before applying it.
Saving is not a toggle for removing a saved result. The current Save action only saves.
Filters and table preferences
Section titled “Filters and table preferences”Use the available repository, author, signal, and text filters to narrow results. If an expected item is missing, check the current view and any persisted exclusions or filtering settings.
Choose visible columns and row density from the table controls. Missing dates or authors display as unavailable; an absent file-update date does not establish when the evidence was collected.
Export workspace results
Section titled “Export workspace results”The Results export dialog offers CSV, TSV, JSON, and JSONL, with selectable fields. Export works on the result set currently available to the page after its filtering.
The application fetches at most 2,500 workspace results per request. This is application behavior, not a customer API endpoint. A table export is not a guaranteed complete workspace archive. Search’s CSV/JSON export is a separate workflow limited to received code-search matches.
Evaluate the evidence
Section titled “Evaluate the evidence”Signals and matched text help prioritize review. They do not independently prove that a secret is valid, a file remains public, or a repository is harmful. Inspect the reference and context before assigning a conclusion.