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

Medium Risk
Changes telemetry gating so analytics events are sent during GitHub Actions runs, which can affect data volume and CI behavior if environment detection is wrong. It’s limited to GitHub Actions via GITHUB_ACTIONS=true, but still touches telemetry/analytics flow.

Overview
Enables telemetry identify and event track calls to be emitted during GitHub Actions workflows (even though CI is treated as a test environment), while continuing to suppress telemetry for local pytest and non-GitHub CI.

Adds is_github_actions() env detection and updates telemetry_utils.identify() and telemetry_utils.log() conditionals accordingly; minor import/comment cleanup in create.py to align CI handling messaging.

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

^{Cursor Bugbot reviewed your changes and found no issues for commit ab15100}

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
monorepo	Ready	Preview, Comment	Feb 4, 2026 9:36pm

[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.