:hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error tracking, logs, and more – capture all the context agents need to diagnose problems, uncover opportunities, and ship fixes. Steer it all from Slack, web, desktop, or the MCP.
Python ab-testingai-analyticsanalyticscdpdata-warehouseexperimentsfeature-flagsjavascriptproduct-analyticspythonreactsession-replaysurveystypescriptweb-analytics
CI and GitHub Actions
.nvmrccontrols the Node.js version for all CI workflows (viaactions/setup-node) — changing it affects every CI job that runs Node- CI uploads test results to Trunk Flaky Tests; the
trunkMCP server in.mcp.jsonqueries per-test flakiness on a PR ormaster(authenticate via/mcp, or aTRUNK_API_TOKENbearer header when headless) — see/debugging-ci-failuresand/fixing-flaky-tests - A workflow edit reaches every open PR before those branches rebase. It runs against the PR merged with master, but a companion change — a new dependency, file, or config — only arrives when the branch rebases. A workflow that starts requiring something unrebased branches lack fails every in-flight PR before its tests run. Make the new behavior degrade gracefully, or gate it. This has broken CI repeatedly.
- Mechanical workflow rules (
timeout-minutes, concurrency, dispatch budget, path filters, gate hygiene) are enforced byhogli lint:workflowsand actionlint, which are the source of truth./authoring-ci-workflowsexplains the reasoning behind each. - A directory of tests that read event properties belongs in
.github/new-events-schema-targets.txt. Backend CI reruns the listed paths against the native-JSON events table. A test outside the list runs on the legacy table only. Add thetest-new-events-schemalabel when a diff needs the whole backend suite on both tables, such as an event ingestion change or event reads tested outside the list. Label while the PR is a draft, or push again after labeling, because label events do not start Backend CI. - A pull request never publishes a package or release.
[lint: github-actions-publish-on-pull-request]A published version is public forever, and a pull request run executes code its author controls. Publish only from apushtomaster, a release tag, or aworkflow_dispatchonmaster. A pull request run only builds and validates, for example with--dry-run. The semgrep rule cannot see a publisher inside a reusable workflow, so gate that job in the called workflow too. Never run a publish command by hand from a pull request branch.build-hogql-parser-npm.ymlis the reference shape.