Open
Conversation
Add an `ask` attribute to commands that shows a y/n confirmation
before executing. If the user declines, the command is skipped but
the task continues with the next command.
Example:
```yaml
cmds:
- cmd: echo "Deploying..."
ask: "Deploy to production?"
- task: run-migrations
ask: "Run database migrations?"
```
Behavior:
- Default: asks for y/n confirmation
- --yes: auto-confirms all asks
- --dry: shows commands without asking
This differs from task-level `prompt:` which cancels the entire task
if declined. Command-level `ask:` only skips the individual command.
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
Add an
askattribute to commands that shows a y/n confirmation before executing. If the user declines, the command is skipped but the task continues with the next command.Example:
This differs from task-level prompt: which cancels the entire task if declined. Command-level ask: only skips the individual command.
The motivation is building interactive workflows (e.g. "commit? → changelog? → push?") where each step can be individually confirmed. This is technically achievable today by combining if: with interactive variables, but the ergonomics are poor and require verbose boilerplate for what should be a simple pattern.