Identify github action logs

[aarondr77]

Description

Identify GitHub action logs

Testing

Please provide a list of the ways you can "access" or use the functionality. Please try and be exhaustive here, and make sure that you test everything you list.

• I have tested this on real data that is reasonable and large
• If I changed the interaction with JupyterLab, I tested that it does not break other programs (like VS Code), and tested that it works "multiple times" in the same notebook.

Documentation

Note if any new documentation needs to addressed or reviewed.

---

Note

Low Risk
Low risk; changes are limited to telemetry gating logic and add a GitHub Actions environment check, but may increase telemetry volume from CI runs.

Overview
Telemetry now distinguishes GitHub Actions from other test environments via a new is_github_actions() helper.

identify() and log() will send Segment/Mixpanel events when running in GitHub Actions (while still skipping local pytest/other CI), enabling CI runs to be attributed to the dedicated mito-github-action user ID.

^{Written by Cursor Bugbot for commit ee47533. This will update automatically on new commits. Configure here.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
monorepo	Ready	Preview, Comment	Jan 29, 2026 4:18pm

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

[cursor]

Unused import is_github_actions in create.py

Low Severity

The function is_github_actions is imported from mito_ai.utils.utils but never used anywhere in create.py. The code at line 70 still uses is_running_test() to set the GITHUB_ACTION_ID, which applies to all CI environments rather than specifically GitHub Actions. This appears to be either an accidental import or an incomplete change where the condition was intended to be updated but wasn't.