feat(feature-flags): add the feature-flags test apps - #4136
Merged
Merged
Conversation
Adds the feature-flags command to the manifest with Next.js and Django apps, and ensureGatewayToken, which mints and caches a phe_ gateway token so --e2e runs can reach the gateway.
This was referenced Sep 23, 2026
Merged
--e2e keeps reading the already-issued gateway token from WIZARD_CI_GATEWAY_TOKEN_FILE, as CI supplies it.
johncwaters
changed the title
gewenyu99
approved these changes
Sep 23, 2026
The diff evaluator has no feature-flags rubric, and the weekly sweep would run these apps through it.
Contributor
If you wanna build it go for it!
Totally valid to reuse |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Feedback wanted: ready to merge. Approve or request changes. Hold the merge until PostHog/wizard#1322 ships (see "Before merge").
basic-integrationNext.js and Django apps, as other commands do. Keep the copies, or run feature-flags e2e against thebasic-integrationapps directly?The wizard's new
feature-flagscommand needs e2e coverage in wizard-workbench.Companion PRs: context-mill (PostHog/context-mill#405) and wizard (PostHog/wizard#1322).
Changes
feature-flagsmanifest entry with two apps: Next.js App Router SaaS and Django 3 SaaS, both without PostHog installed. Markede2eOnly, so CI grades them only through--e2eassertions and never through the diff evaluator, which has no feature-flags rubric.Before merge: PostHog/wizard#1322 must ship and the backend must register
feature-flagsinWIZARD_GATEWAY_PROGRAM_IDS. The weekly scheduled sweep runs every e2e app against wizard main, so merging earlier would add failing legs.Test plan
pnpm wizard-ci feature-flags/next-js/15-app-router-saas --e2eandpnpm wizard-ci feature-flags/django/django3-saas --e2epass against a test project, starting with no example flags in the project, using a gateway token minted locally. Next.js creates both example flags; Django creates only the backend flag, because its templates contain no scripts.LLM context
Written with Claude Code.