Skip to content

fix(wfctl): register cmd-build pipeline in wfctl.yaml #415

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
intel352 merged 1 commit into from
Apr 19, 2026
Merged

fix(wfctl): register cmd-build pipeline in wfctl.yaml #415

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions cmd/wfctl/wfctl.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -207,6 +207,17 @@ pipelines:
config:
command: build-ui

cmd-build:
trigger:
type: cli
config:
command: build
steps:
- name: run
type: step.cli_invoke
config:
command: build

Comment on lines +210 to +220

Copilot AI Apr 19, 2026

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider adding a small regression test that loads cmd/wfctl/wfctl.yaml, builds an engine with the CLI trigger + step.cli_invoke registered, and asserts the CLITrigger has a mapping for "build" (and ideally all commands in cmd/wfctl/main.go's commands map). This would prevent future command additions from being missed in the embedded YAML again.

Copilot generated this review using guidance from organization custom instructions.
cmd-ui:
trigger:
type: cli
Expand Down
Loading