Skip to content

feat(harness): brand hog with a hedgehog glyph instead of pi's π#3316

Draft
adboio wants to merge 1 commit into
mainfrom
posthog-code/hog-branding-hedgehog-glyph
Draft

feat(harness): brand hog with a hedgehog glyph instead of pi's π#3316
adboio wants to merge 1 commit into
mainfrom
posthog-code/hog-branding-hedgehog-glyph

Conversation

@adboio

@adboio adboio commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

Problem

The hog harness is built on pi, and pi's default terminal title/header uses a π glyph. The hog-branding extension already strips that prefix down to a plain hog, but nothing carries PostHog's hedgehog mascot through — so the branding reads as pi's leftover symbol rather than as PostHog.

Why: Requested to make the harness header feel fun and on-brand — a hedgehog instead of the pi symbol.

Changes

  • Add a BRAND_GLYPH (🦔) constant to the hog-branding extension and front both the TUI header line and the OS terminal title with it, so they render as 🦔 hog … in place of pi's π.

Header line: 🦔 hog (A Pi distribution by PostHog) v<version>
Terminal title: 🦔 hog - <session> - <cwd>

How did you test this?

  • pnpm --filter @posthog/harness exec vitest run — full harness suite passes (472 tests), including the updated hog-branding header/title assertions.
  • pnpm --filter @posthog/harness typecheck — clean.
  • biome lint packages/harness/src/extensions/hog-branding/ — clean.

Automatic notifications

  • Publish to changelog?
  • Alert Sales and Marketing teams?

Created with PostHog Code

The hog-branding extension already replaced pi's default `π` title prefix
with a plain "hog", but nothing carried PostHog's mascot through. Front both
the TUI header line and the OS terminal title with the 🦔 hedgehog glyph so
the harness reads as posthoggy rather than pi's bare symbol.

Generated-By: PostHog Code
Task-Id: 5d9d5188-0670-497f-b42f-caca6ae34df5
@trunk-io

trunk-io Bot commented Jul 9, 2026

Copy link
Copy Markdown

Merging to main in this repository is managed by Trunk.

  • To merge this pull request, check the box to the left or comment /trunk merge below.

After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here

@github-actions

github-actions Bot commented Jul 9, 2026

Copy link
Copy Markdown

React Doctor found no issues in the changed files. 🎉

Reviewed by React Doctor for commit a6030bd.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant