Fleet command multi clone
- Dominant language
- Shell
- Stars
- 11.2k
- Forks
- 1.9k
- Avg merge
- 14h 16m
- Merged PRs (30d)
- 6
Description
### Describe the feature or problem you'd like to solve
In order to not squash file changes, clone repo to multiple directories and have git as the communication mechanism
### Proposed solution
Allow /fleet to clone the repository multiple times and rely on git functions to handle file conflicts and file squash incidents.
### Example prompts or workflows
_No response_
### Additional context
_No response_
Contributor guide
Research direction
Start by tracing the /fleet command and its existing repository-cloning workflow. Determine how multiple clone directories and git-based communication should fit the current behavior; the work is done when /fleet can manage multiple clones without squashing file changes or leaving conflicts ambiguous.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, shell
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100