Automatically submitted on behalf of the user by an AI agent.
Request
Please add PowerShell (pwsh) completion support to the v2 executor CLI. PowerShell users currently cannot generate native completions: executor --help lists only bash, zsh, fish, and sh for --completions.
Current behavior
On Windows, running:
executor --completions pwsh
is not supported by the listed choices. Also, requesting Bash completions for a nested command currently appears to emit only the marker, with no completion entries:
executor apps --completions bash
Output:
###-begin-executor-completions-###
Expected behavior
pwsh is an accepted value for --completions and prints a PowerShell-native completion script suitable for registering with Register-ArgumentCompleter.
- Generated completions cover the v2 CLI's subcommands and flags, including nested commands such as
apps.
Environment
- Windows / PowerShell (
pwsh)
- Executor v2 CLI
I searched the existing issues for PowerShell completion support and did not find a duplicate.
Automatically submitted on behalf of the user by an AI agent.
Request
Please add PowerShell (
pwsh) completion support to the v2executorCLI. PowerShell users currently cannot generate native completions:executor --helplists onlybash,zsh,fish, andshfor--completions.Current behavior
On Windows, running:
executor --completions pwshis not supported by the listed choices. Also, requesting Bash completions for a nested command currently appears to emit only the marker, with no completion entries:
executor apps --completions bashOutput:
Expected behavior
pwshis an accepted value for--completionsand prints a PowerShell-native completion script suitable for registering withRegister-ArgumentCompleter.apps.Environment
pwsh)I searched the existing issues for PowerShell completion support and did not find a duplicate.