posthog-ci-integration

Configure PostHog CI/CD integration with GitHub Actions and testing.Use when setting up automated testing, configuring CI pipelines,or integrating PostHog tests into your build process.Trigger with phrases like "posthog CI", "posthog GitHub Actions","posthog automated tests", "CI posthog".

⭐939stars🔀114forks📁View on GitHub🕐Updated Jan 11, 2026⬇️2downloads

When & Why to Use This Skill

This Claude skill automates the setup and configuration of PostHog CI/CD integrations within GitHub Actions. It helps developers ensure data integrity and analytics reliability by streamlining the creation of automated testing pipelines, secure secret management, and integration test suites for PostHog environments.

Use Cases

  • Automating the creation of GitHub Actions workflows to run PostHog integration tests on every pull request to prevent breaking analytics.
  • Securely configuring PostHog API keys and environment variables using GitHub CLI (gh) integration.
  • Developing integration test suites that verify PostHog client connectivity and health status before code deployment.
  • Setting up release workflows that perform production-readiness checks to ensure tracking is functional in live environments.
  • Configuring branch protection rules that require successful PostHog integration checks before merging code to main branches.
nameposthog-ci-integration
description|
allowed-toolsRead, Write, Edit, Bash(gh:*)
version1.0.0
licenseMIT
authorJeremy Longshore <jeremy@intentsolutions.io>

PostHog CI Integration

Overview

Set up CI/CD pipelines for PostHog integrations with automated testing.

Prerequisites

  • GitHub repository with Actions enabled
  • PostHog test API key
  • npm/pnpm project configured

Instructions

Step 1: Create GitHub Actions Workflow

Create .github/workflows/posthog-integration.yml:

name: PostHog Integration Tests

on:
  push:
    branches: [main]
  pull_request:
    branches: [main]

env:
  POSTHOG_API_KEY: ${{ secrets.POSTHOG_API_KEY }}

jobs:
  test:
    runs-on: ubuntu-latest
    env:
      POSTHOG_API_KEY: ${{ secrets.POSTHOG_API_KEY }}
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: '20'
          cache: 'npm'
      - run: npm ci
      - run: npm test -- --coverage
      - run: npm run test:integration

Step 2: Configure Secrets

gh secret set POSTHOG_API_KEY --body "sk_test_***"

Step 3: Add Integration Tests

describe('PostHog Integration', () => {
  it.skipIf(!process.env.POSTHOG_API_KEY)('should connect', async () => {
    const client = getPostHogClient();
    const result = await client.healthCheck();
    expect(result.status).toBe('ok');
  });
});

Output

  • Automated test pipeline
  • PR checks configured
  • Coverage reports uploaded
  • Release workflow ready

Error Handling

Issue Cause Solution
Secret not found Missing configuration Add secret via gh secret set
Tests timeout Network issues Increase timeout or mock
Auth failures Invalid key Check secret value

Examples

Release Workflow

on:
  push:
    tags: ['v*']

jobs:
  release:
    runs-on: ubuntu-latest
    env:
      POSTHOG_API_KEY: ${{ secrets.POSTHOG_API_KEY_PROD }}
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: '20'
      - run: npm ci
      - name: Verify PostHog production readiness
        run: npm run test:integration
      - run: npm run build
      - run: npm publish

Branch Protection

required_status_checks:
  - "test"
  - "posthog-integration"

Resources

Next Steps

For deployment patterns, see posthog-deploy-integration.