Repository navigation
ci(rebuild-content): add challenge-widget-enabled input to bake challenge specs (#2362) - #2433
Merged
Merged
Conversation
…enge specs (#2362) The challenge-widget wireup (#2428) gates challenge-spec generation behind the CHALLENGE_WIDGET_ENABLED build-time env var in fetch-tutorials, but the rebuild-content workflow never passed it — so a rebuild could never actually generate/bake the panels even with the admin flag flipped. Adds a `challenge-widget-enabled` boolean workflow_dispatch input (default false, DEV-only) and plumbs it to the Fetch tutorials step as CHALLENGE_WIDGET_ENABLED. Shares the existing ai-author-build-cap LLM ceiling. repository_dispatch runs have no inputs, so the gate stays off there — manual opt-in only. After #2428 is deployed to DEV, a rebuild with this input true is what actually bakes the challenge panels into tutorial-data. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
This was referenced Sep 19, 2026
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
1 participant
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.
What & why
The challenge-widget wireup (#2428, merged to DEV) gates challenge-spec generation behind the
CHALLENGE_WIDGET_ENABLEDbuild-time env var infetch-tutorials. Butrebuild-content.ymlnever passed that env var — so a content rebuild could never actually generate or bake the challenge panels, even with the admin flag flipped. This closes that gap.Change
One file. Adds a
challenge-widget-enabledbooleanworkflow_dispatchinput (defaultfalse, DEV-only) and plumbs it to the Fetch tutorials step asCHALLENGE_WIDGET_ENABLED. Shares the existingai-author-build-capLLM ceiling.repository_dispatchruns (source-repo pushes) have noinputs, so the expression resolves empty → gate stays off there. Manual opt-in only — the widget stays dark unless someone dispatches a rebuild with this inputtrue.How this fits the sequence
Once #2428 is deployed to DEV (the island bundle + layout land, and the admin flag surfaces), the human-testable path is:
flag.challengeWidget(record/kill switch),rebuild-content.ymlon DEV withchallenge-widget-enabled=true— this PR is what makes step 2 actually bake the panels.Verification
YAML parses (
yq): new input appears inworkflow_dispatch.inputs; the Fetch-tutorials step carriesCHALLENGE_WIDGET_ENABLED: ${{ inputs.challenge-widget-enabled == true && 'true' || '' }}. No behavior change when the input is unset/false (the default).🤖 Generated with Claude Code