feat(hogli): add is_posthog_dev telemetry property#53801
Draft
feat(hogli): add is_posthog_dev telemetry property#53801
Conversation
rnegron
commented
Apr 8, 2026
| return None | ||
|
|
||
|
|
||
| @functools.lru_cache(maxsize=1) |
Contributor
|
⏭️ Skipped snapshot commit because branch advanced to The new commit will trigger its own snapshot update workflow. If you expected this workflow to succeed: This can happen due to concurrent commits. To get a fresh workflow run, either:
|
Contributor
Query snapshots: Backend query snapshots updatedChanges: 1 snapshots (1 modified, 0 added, 0 deleted) What this means:
Next steps:
|
Contributor
|
🎭 Playwright report · View test results →
These issues are not necessarily caused by your changes. |
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.
Problem
The hogli DevEx dashboard mixes PostHog engineer usage with external contributor usage. There's no way to filter by audience, making it hard to understand internal adoption vs community usage.
Changes
Adds a boolean
is_posthog_devevent property to all hogli telemetry events. Detected by checking ifgit config user.emailends with@posthog.com. The actual email is never sent -- just a boolean.How did you test this code?
_is_posthog_dev()covering: PostHog email, non-PostHog email, git config failure, subprocess exceptionNo manual testing beyond unit tests -- this was agent-authored.
No changelog, no docs update.
LLM context
Agent-authored PR. Claude Code session.