Skip to content

chore: open-source readiness cleanup#358

Merged
brendanjryan merged 1 commit into
mainfrom
open-source-readiness
Mar 18, 2026
Merged

chore: open-source readiness cleanup#358
brendanjryan merged 1 commit into
mainfrom
open-source-readiness

Conversation

@brendanjryan

Copy link
Copy Markdown
Collaborator

Open-source readiness fixes

Prepares the repo for public release by removing internal artifacts and hardcoded keys.

Changes

  1. Remove checkpoint-fix.yml — Internal CI workflow containing internal Checkpoint app URLs, checkpoint@tempo.xyz email, and references to internal secrets (CHECKPOINT_SECRET, GH_PAT, AMP_API_KEY)

  2. Move PostHog key to env var — The PostHog project key (phc_...) was hardcoded in _layout.tsx. Now reads from VITE_POSTHOG_KEY env var, with a null guard so analytics is disabled when unset. Added to .env.example.

  3. Remove TODO commentllms-token-count.yml had a TODO about replacing build steps "once the site is public" — removes the comment that reveals internal launch plans.

Not changed (verified OK)

  • .vercel/ — Already in .gitignore and not tracked
  • AGENTS.md — Reviewed: contains documentation conventions and contributing guidance only, no sensitive content
  • tempoxyz/tempo references — Repo is public, links are fine
  • vocs pinning — Vocs v2 has no stable npm release (only pkg.pr.new previews); no better option available yet
  • siwx-audit.txt — Was untracked (never committed), deleted from working tree

Deploy note

Add VITE_POSTHOG_KEY=phc_aNlTw2xAUQKd9zTovXeYheEUpQpEhplehCK5r1e31HR to Vercel environment variables to maintain analytics.

- Remove checkpoint-fix.yml (internal CI workflow with internal URLs, secrets, emails)
- Move PostHog key from hardcoded to VITE_POSTHOG_KEY env var
- Remove TODO comment in llms-token-count.yml revealing internal plans
- .vercel/ already gitignored and untracked (confirmed)
- AGENTS.md reviewed: no sensitive content, appropriate as contributing guide
- tempoxyz/tempo is public, references are fine
- vocs pinning: v2 has no stable npm release yet (only pkg.pr.new previews), keeping current
@vercel

vercel Bot commented Mar 18, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
mpp Ready Ready Preview, Comment Mar 18, 2026 3:05am

Request Review

@brendanjryan brendanjryan merged commit 2ded514 into main Mar 18, 2026
8 checks passed
@brendanjryan brendanjryan deleted the open-source-readiness branch March 18, 2026 03:06

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3a0b56938d

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread src/pages/_layout.tsx
Comment on lines 18 to +19
if (!import.meta.env.PROD) return;
if (!POSTHOG_SNIPPET) return;

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Preserve PostHog init until deploy envs are updated

In any production build where VITE_POSTHOG_KEY has not been added yet, usePostHog() now returns at _layout.tsx and never loads PostHog. That means every captureEvent(...) call in src/lib/posthog.ts is silently dropped after the retry loop, so this change disables all analytics on existing deployments until the new env var is provisioned out of band. Because the repo change only updates .env.example, I'd keep the current key as a fallback or fail the build when the variable is missing.

Useful? React with 👍 / 👎.

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