Repository navigation
docs: title the migration page with its H1, and move the posthog.com SDK page into the reference - #1244
docs: title the migration page with its H1, and move the posthog.com SDK page into the reference#1244gewenyu99 wants to merge 3 commits into
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
posthog-python Compliance ReportDate: 2026-11-12T17:44:03.074817+00:00 ✅ All Tests Passed!270/270 tests passed Capture_V1 Tests✅ 95/95 tests passed View Details
Capture_Ai Tests✅ 5/5 tests passed View Details
Feature_Flags Tests✅ 17/17 tests passed View Details
Feature_Flags_V4 Tests✅ 149/149 tests passed View Details
Feature_Flags_Local_Evaluation Tests✅ 4/4 tests passed View Details
|
SDK performance: posthog-python1 change worth reviewing: 1 observed regression. Flags require at least a 5% change in the median and all six pairs agreeing on direction. This is a noise filter, not proof of a performance change or a CI gate.
View all results
Values are medians of paired measurements. Not flagged does not mean unchanged. Unavailable means a measurement could not be provided, not zero. Estimated allocation measurements retain their instrumentation uncertainty. RSS measures the whole process, not just SDK allocations; observed peaks are sampled checkpoints. Paired ranges in the diagnostics describe variability, not confidence intervals. Each shard uses its own runner; compare Before PR against With PR within a row, not across shards. Compared 102 metric rows; 102 rows shown in all results. Omitted or shortened data remain in |
The posthog.com Python SDK pages redirect to this reference once 8.0.0 ships, so their setup, how-to, and configuration sections now live in docs/getting-started.md. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Combined into #1245. |
💡 Motivation and Context
The migration page on posthog.com shows two titles: the front matter title "PostHog Python SDK migration guides", then the guide's own H1. With one guide, the page now uses the guide's H1 as its title and drops the H1 from the body. With more than one guide, nothing changes.
Content from the posthog.com Python SDK page
posthog.com retires its hand-written Python SDK page and redirects it to the Python reference. So nothing is lost, this PR moves everything on that page that the reference didn't already say into
docs/getting-started.md, which the reference shows as its "Getting started" section. Examples are setup variants, how-to sections, feature flag usage, and configuration guidance.💚 How did you test it?
Two new tests in
posthog/test/test_reference_markdown.pycover one guide and several guides.pytest posthog/test/test_reference_markdown.pypasses (8).ruff format --checkpasses.ruff checkreports the same 5 findings as onmain.📝 Checklist
🤖 Generated with Claude Code