Remove active/passive campaign distinction#11071
Conversation
Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com>
Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com>
|
@copilot Using dispatch, the campaign orchestrator can also give workers input based on the decisions it makes. |
Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com>
Updated the workflow execution template to document this capability. The orchestrator can now pass input parameters to workers (e.g., |
|
@copilot Ensure that campaign associated worker workflows can accept dispatch inputs from orchestrator. |
Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com>
Updated the worker workflow creation template to include |
|
@copilot recompile campaigns |
Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com>
Remove Active/Passive Campaign Distinction
All campaigns are now "active" in that the orchestrator can make decisions and dispatch workflows.
Changes Made
Implementation Details
pkg/campaign/orchestrator.go:
if len(spec.Workflows) > 0checkpkg/campaign/template.go:
add1template function for 1-based indexing in workflow listsTemplate files:
.lock.ymlfiles to focus on source.mdfilesinputs: {priority: "high", target: "security"})workflow_dispatchwith exampleinputs(priority, target)${{ github.event.inputs.INPUT_NAME }}in workflow markdownImpact
Testing
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.