github / github/app

[Requests and ideas] 🚀 Feature Request: Separate Configuration for “Storage Location” (Worktrees vs Main Repo)

Abierto
#208 1 comentario 0 reacciones 0 asignados Ver en GitHub
Requests and ideas
Lenguaje dominante
Sin datos de lenguaje
Estrellas
2.1k
Forks
153
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

**Mood:** 😊
**Category:** Requests and ideas

# 🚀 Feature Request: Separate Configuration for “Storage Location” (Worktrees vs Main Repo)

## Summary
Please separate the **Storage Location** configuration into two independent settings. My workflow requires storing **worktrees** in a different location from my primary repositories, but the current single setting forces both to share the same path.

## Problem
I keep my main repositories on a dedicated **dev drive** where performance, backups, and organization matter.
However, my **worktrees** are intentionally placed on a **scratch drive** — a location where I can freely create, delete, and experiment without worrying about clutter or long‑term retention.

Right now, the GitHub Copilot App only exposes a single “Storage Location” setting, which applies to both:

- The main repo clone
- Any worktrees created from that repo

This creates friction because the two types of content have very different lifecycles and storage requirements.

## Why This Matters
Worktrees are:

- Temporary
- Disposable
- Often numerous
- Not something I want mixed with my main development repos

Repos, on the other hand, are:

- Long‑lived
- Backed up
- Carefully organized

Having both share the same storage path makes it harder to manage disk usage and maintain a clean development environment.

## Proposed Solution
Add **two separate configuration options**:

1. **Repository Storage Location**
- Where the main repo is cloned and stored
2. **Worktree Storage Location**
- A separate path for all worktrees created by the Copilot App

This would allow developers to keep repos on a stable drive while directing worktrees to a scratch or temporary drive.

## Benefits
- Cleaner separation of long‑term vs disposable content
- Better disk management
- More flexibility for advanced Git workflows
- Aligns with how many developers already structure their environments manually

## Example
**Current:**
```
Storage Location: D:\Dev
```

**Desired:**
```
Repository Storage Location: D:\Dev
Worktree Storage Location: E:\Scratch
```

## Closing Thoughts
This change would significantly improve workflows for anyone using worktrees heavily, especially in large monorepos or multi‑branch development environments. It’s a small configuration enhancement with a big quality‑of‑life impact.

---
| Field | Value |
| --- | --- |
| App version | 0.2.6 |
| OS | Windows 10.0.26200 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Day 2 (Week 1) |

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.