[General] The way worktrees are being named is very confusing and not helpful.
- Vorherrschende Sprache
- Keine Sprachdaten
- Sterne
- 2.1k
- Forks
- 153
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
**Mood:** 😊
**Category:** General
The way worktrees are being named is very confusing and not helpful. If there are multiple worktrees, it becomes very difficult to figure out what it was related to. Just having the username in the work tree is not helping. There should be a way to tag the repository, maybe branch, and there should be more options in general to decide the name of the work tree rather than having random names assigned to it.
---
| Field | Value |
| --- | --- |
| App version | 1.0.16 |
| OS | macOS 26.5.0 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Week 7 |
Beitragsleitfaden
Rechercherichtung
No files or tests are named. Start by locating the code that creates and names worktrees, then review how repository, branch, and username information are currently available. Done should include an agreed naming design with user-configurable options and coverage for the resulting worktree names.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- git
- Bereich
- desktop, tooling
- Issue-Typ
- Feature
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Aktivitätsstatus
- Ruhig
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 35/100