ci: rename direct_prompt to prompt in api-sync workflow#24
Merged
Conversation
claude-code-action@v1 renamed the autonomous prompt input from
`direct_prompt` to `prompt`. The old name now triggers a warning
("Unexpected input(s) 'direct_prompt'") and is silently ignored, so
the action waits for a trigger phrase or label that the workflow
never provides. The Implement step exits successfully having done
nothing.
This is exactly what happened on PR #23, which landed with only the
spec bump and required manual implementation. With this fix, future
api-sync runs should auto-implement new endpoints as designed.
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
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.
Summary
claude-code-action@v1renamed the autonomous prompt input fromdirect_prompttoprompt. The old name produces a warning (Unexpected input(s) 'direct_prompt') and is silently ignored, so the action waits for a trigger phrase or label the workflow never provides. The Implement step exits successfully having done nothing.This is exactly what happened on PR #23: the daily api-sync run detected two new endpoints (
GET /v2/projects/{p}/deploymentsandGET /v2/projects/{p}/deployments/{d}), opened a PR with the spec bump, but the Implement step was a no-op. The endpoints had to be implemented by hand.With this one-line fix, future api-sync runs auto-implement new endpoints as designed.
Test plan
grep direct_prompt .github/workflows/*.ymlreturns nothinggh workflow run api-sync.yml)