brainstorming
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
posthog-ci-integrationConfigure 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".
Independent GitHub snapshot · Automated classification · Original documentation governs
Set up CI/CD pipelines for PostHog integrations with automated testing.
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
gh secret set POSTHOG_API_KEY --body "sk_test_***"
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');
});
});
| 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 |
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
required_status_checks:
- "test"
- "posthog-integration"
For deployment patterns, see posthog-deploy-integration.