Repository navigation
feat(cli): tag CI invocations in telemetry - #1753
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
This branch was previously deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Commands without an
agenttag are currently grouped as human usage, which also includes CI jobs. Add an explicitis_citag (trueorfalse) to CLI and library telemetry so dashboards can separate those invocations while preserving the identity of agents running in CI.Reuse the existing environment detector for telemetry, build uploads, and snapshot uploads without changing its matching behavior or adding dependencies. Outgoing event and command transaction tests cover generic and provider-specific CI markers, false/unset values, and preserved agent identity.
The developer guide documents the dashboard split, retaining the existing command filters and aggregate:
!agent:""agent:"" is_ci:trueagent:"" is_ci:falseagent:"" is_ci:""Dashboard updates should follow a CLI release containing the tag. Older events without
is_ciremain unknown; the Human label still includes undetected local automation.Validated with root typecheck and lint, and the full root test suite on Linux x64 / Node 24 / UTC with Spotlight disabled: 15,877 tests passed, 72 skipped.