Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Refactor] Decouple Git from Conductor commands to support multi-VCS (JJ, Piper).

Open
  • Is something wrong?
#70 0 comments 1 reaction 1 assignee View on GitHub

@mahimashanware is already working on this.

Since Jan 16, 2026.

Assessment

This issue has not been assessed yet.

Description

area:revert feature p1

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

  • Phase 1: Extraction
    • Refactor conductor commands to remove direct Git dependencies.
    • Rename templates/workflow.md to templates/git_workflow.md.
  • Phase 2: The Interface
    • Implement a mechanism to select the correct workflow file based on the detected VCS.
  • Phase 3: New Systems
    • Add templates/jj_workflow.md.
    • Update revert.toml logic to handle non-Git revert flows.

Related Issues

  • Tracks implementation for #52
Dominant language
Python
Stars
3.7k
Forks
297
Avg merge
9m
Merged PRs (30d)
1

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from gemini-cli-extensions/conductor

All issues in gemini-cli-extensions/conductor

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.