Overview
Currently, Conductor commands are tightly coupled to Git. We need to refactor this to support other VCS systems like Jujutsu (JJ) and Piper.
This issue tracks the work to remove Git-specific logic from the core commands and move them into specific workflow templates.
Architecture Changes
1. Workflow Templates
We need to move the default workflow from being hardcoded to Git.
- Current:
templates/workflow.md is the default.
- Plan: Rename the current
templates/workflow.md to a Git-specific workflow (templates/git_workflow.md) and make the system select the correct workflow based on the user's VCS.
2. Revert Flow
The revert logic in commands/conductor/revert.toml currently assumes Git behavior. We need to:
- Abstract the "revert" concept so it works for various VCS.
- Create separate configuration or strategy patterns for each VCS.
Task List
Related Issues
Overview
Currently, Conductor commands are tightly coupled to Git. We need to refactor this to support other VCS systems like Jujutsu (JJ) and Piper.
This issue tracks the work to remove Git-specific logic from the core commands and move them into specific workflow templates.
Architecture Changes
1. Workflow Templates
We need to move the default workflow from being hardcoded to Git.
templates/workflow.mdis the default.templates/workflow.mdto a Git-specific workflow (templates/git_workflow.md) and make the system select the correct workflow based on the user's VCS.2. Revert Flow
The revert logic in
commands/conductor/revert.tomlcurrently assumes Git behavior. We need to:Task List
conductorcommands to remove direct Git dependencies.templates/workflow.mdtotemplates/git_workflow.md.templates/jj_workflow.md.revert.tomllogic to handle non-Git revert flows.Related Issues