fix: nextjs-tracker workflow fails because prompt_file is not a valid action input

[southpolesteve]

Summary

• The ask-bonk action doesn't support a prompt_file input (valid inputs: model, agent, prompt, mentions, permissions, oidc_base_url, forks, variant, token_permissions, opencode_version, opencode_dev)
• The first scheduled run at 08:11 UTC today failed immediately with: PROMPT input is required for scheduled and workflow_dispatch events
• Fix: write the prompt to a multiline $GITHUB_OUTPUT in the "Build tracker prompt" step and reference it via prompt: ${{ steps.build_prompt.outputs.prompt }}

Failed run: https://github.com/cloudflare/vinext/actions/runs/23531220466

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/vinext@687

commit: fa90bc8

[github-actions]

Example	Preview	Production	Original
app-router-cloudflare	preview	production
pages-router-cloudflare	preview	production
app-router-playground	preview	production	original
realworld-api-rest	preview	production
nextra-docs-template	preview	production
benchmarks	preview	production
hackernews	preview	production	original

[southpolesteve]

/bigbonk review

[ask-bonk]

Correct fix. The prompt_file input doesn't exist on the ask-bonk action, and the multiline heredoc output pattern (<<PROMPT_DELIM / PROMPT_DELIM) is the standard way to pass multi-line strings through $GITHUB_OUTPUT.

Also good catch removing the unused HOURS variable that was shadowing the one already set in the prior step.

[ask-bonk]

Approved the PR. The fix is clean:

1. Replaces the invalid prompt_file input with the supported prompt input
2. Uses the standard $GITHUB_OUTPUT heredoc pattern to pass the multiline prompt between steps
3. Adds the missing id: build_prompt on the step so the output can be referenced
4. Removes the unused HOURS variable that was redundantly re-declared (it's already set in the prior "Fetch recent commits" step)

github run