Repository navigation
Ship the email send API as one reviewed draft PR #477
Description
Question
Is the email send API's PostHog/posthog code a reviewed draft pull request?
The integration branch spec/email-send-api on Silthus/posthog collects #469, #470, #471, #472 and #473. It is stacked on the migration-only PR of #468, which ships alone as the repo rules require. Open one draft PR on PostHog/posthog from the integration branch, stacked on #468's PR, review the whole branch against Spec: email send API with the spec as the oracle, fix every finding that holds, and hand it off. The diff touches merge-risk danger areas (auth and scopes, service-to-service auth, real sends and billing), so the review is qa-swarm.
Activity
Silthus commentedon Oct 14, 2026
Integration branch:
spec/email-send-apion Silthus/posthog, created fromce0843adff0(the reviewed head of #468's PR #116915). The ship PR stacks on PostHog#116915.Silthus commentedon Oct 16, 2026
Closed: the map converged on the upstream transactional email stack that landed on PostHog/posthog master on 2026-10-16 (send through
POST /messaging_templates/{id}/send/). This lane built the parallel/emailspath and is no longer needed. See the map, #461, "Orchestration blocker".