ci: suppress CLI telemetry in workflows#210
Merged
Merged
Conversation
CI workflows that build/run archgate from source were emitting PostHog telemetry tagged with in-development version strings from package.json (e.g. v0.29.0-prerelease). This polluted product-usage numbers with CI-from-source events that look like real user installs. Set ARCHGATE_TELEMETRY="0" as a top-level workflow env var so the CLI's isEnvTelemetryDisabled() opt-out short-circuits emission during CI runs. The env var is a no-op for workflows that don't invoke the CLI, so it is applied broadly to all workflows that install Bun / run the repo's scripts. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Deploying archgate-cli with
|
| Latest commit: |
8053174
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://7f7484de.archgate-cli.pages.dev |
| Branch Preview URL: | https://ci-suppress-cli-telemetry.archgate-cli.pages.dev |
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
1 participant
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.
Problem
CI workflows that build and run
archgatefrom source were emitting PostHog telemetry tagged with in-development version strings frompackage.json(e.g.v0.29.0-prerelease). Each CI run looks like a real user installation in PostHog product-usage dashboards, inflating adoption numbers and polluting version distributions with prerelease tags that never ship.Fix
Set
ARCHGATE_TELEMETRY: "0"as a top-level workflowenv:block on every workflow that installs Bun or runs repo scripts. The CLI'sisEnvTelemetryDisabled()short-circuits emission when this env var is set, so CI-from-source invocations (bun run src/cli.ts,bunx archgate, compiled smoke-test binaries) no longer reach PostHog. The env var is a no-op for workflows that don't invoke the CLI, so applying it broadly is safe.Files touched
Added
env.ARCHGATE_TELEMETRY: "0":.github/workflows/code-pull-request.yml— runsbun run validate(tests exercise CLI code paths).github/workflows/release-binaries.yml— runsbun run validateand builds the CLI binary.github/workflows/release.yml— runsbun run validate.github/workflows/smoke-test-linux.yml— runs the compiled binary directly.github/workflows/smoke-test-windows.yml— runs the compiled binary directly.github/workflows/update-llms.yaml— runs a Bun script from the repo.github/workflows/update-lock.yaml— runsbun installSkipped:
.github/workflows/track-adoption.yml— puregh search+curlto PostHog; does not install Bun or invoke the CLI. (This workflow is itself the intentionalarchgate_repo_seenevent emitter.)