Problem
AutoPR supports only a single workflow configuration. This forces users to choose between a full investigation-to-PR pipeline and nothing — there's no way to run a lighter "just refine this ticket" workflow or a custom sequence for a specific use case. Different tasks warrant different workflows and there's currently no way to express that.
Solution
- Extend the workflow config format to support a named list of workflows (e.g.
workflows: [{name: full, ...}, {name: refine-only, ...}]).
- Add a
default_workflow config key.
- Update the CLI (
auto-pr run) to accept an optional --workflow <name> flag.
- Update the web UI to allow selecting a workflow when starting a ticket run.
- Store the selected workflow name on the run record so the correct config is used throughout.
Problem
AutoPR supports only a single workflow configuration. This forces users to choose between a full investigation-to-PR pipeline and nothing — there's no way to run a lighter "just refine this ticket" workflow or a custom sequence for a specific use case. Different tasks warrant different workflows and there's currently no way to express that.
Solution
workflows: [{name: full, ...}, {name: refine-only, ...}]).default_workflowconfig key.auto-pr run) to accept an optional--workflow <name>flag.