Skip to content

Watchdogs

Watchdogs monitor incoming GitHub activity and add matching evidence to your workspace. Open Watchdogs in your workspace to create and manage them.

Use a Watchdog when you want to keep watching for a domain, configuration marker, code pattern, or other text as new changes are processed.

The monitoring pipeline processes incoming public GitHub push activity and evaluates rules against commit changes. File-content conditions examine added lines, rather than an entire repository checkout.

Monitoring is asynchronous and depends on activity reaching the pipeline. An active monitor means it is eligible to process work; it does not guarantee immediate matches or complete coverage of every public commit. Historical code search is a separate workflow.

  1. Open the workspace’s Watchdogs page.
  2. Select New watchdog.
  3. Add a rule and keep its Effect set to Match.
  4. Choose a property, operator, and value for each condition.
  5. Choose AND when every condition must hold, or OR when any condition is enough.
  6. Add an optional name, such as “Example API references”.
  7. Set Max Results Per Day.
  8. Optionally enable Email me when the first result arrives.
  9. Select Create Watchdog.

To find a domain in new Python code while avoiding test paths, use one Match rule with AND:

PropertyOperatorValue
File Contentcontainsapi.example.com
Languageispython
File Pathnot containstests/

All conditions must hold for the same added-line context. Multiple required content strings must occur on the same added line; they are not matched across separate lines of the file.

The creation and editing forms offer Generate Rules with AI. Describe the pattern you want, then inspect every generated condition before saving.

Generated rules replace the rules currently shown in the editor. Check the effect, AND/OR choice, property names, and operators. Use the rule reference to check whether the generated rule fits the live scanner’s supported behavior.

Open Saved results in the sidebar and choose All results to review incoming matches. A monitor’s result link can open a monitor-specific Results view.

Inspect the matched line and available repository or commit reference, then save useful evidence or ignore irrelevant unreviewed results.

The creation form defaults to 1,000 results per day and accepts a cap from 1 to 1,000. The monitor’s result-count window lasts 24 hours from its window start; it is separate from the account’s search allowance, which resets at midnight UTC.

The first-result email option sends one notification for that monitor. It does not send an email for every match. The monitor continues running after the notification.

The monitor list shows status and result counts. Use its action menu to Edit, Pause, or Delete a monitor.

Pausing removes it from active monitoring. Deleting removes the monitor and its rules and requires confirmation. The current action menu has a Pause control; it does not expose a Resume control.

Active-monitor limits apply across your account. Pausing a monitor frees active capacity for another monitor.

Keep Effect set to Match. Although the builder offers Exclude, the live scanner skips Exclude rules rather than applying them as exclusions. To exclude a path or term, use not contains inside the same AND Match rule.

Rules are evaluated independently. Their visual order is not a first-match-wins priority system. Add explicit conditions to each rule that needs them.

See Watchdog rule reference for case sensitivity, line-based matching, and property meanings.