[Bugs] The worktree branch name is too oppinionated.
- Langage dominant
- Aucune donnée de langage
- Étoiles
- 2.1k
- Forks
- 153
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
**Mood:** 😊
**Category:** Bugs
The worktree branch name is too oppinionated.
We have a naming scheme which, even though I have written it in instructions in the app, is not honoured.
The auto-namer do follow a bit of the naming scheme as defined, but prepend my username nonetheless, leaving the branch name as a weird hodgepodge of two naming schemes.
If I tell the agent to rename the branch, the answer is that it can only rename once and that the tool rejects rename attempts. Which is again an oppionated approach.
My workaround is to explictly tell copilot to hold off on pushing by itself, then being explicit about what the remote branch should be called - so local branch name and remote branch are not the same. But sometimes even that fails, and my PRs are created with a wrong name, breaking some auto flows that detect the ticket id in the branch name to bind the PR and the ticket, so I have to see the connection is broken, and then create that connection manually.
---
| Field | Value |
| --- | --- |
| App version | 0.2.13 |
| OS | Windows 10.0.26200 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Week 2 |
Guide de contribution
Ouvrir le guide de contribution
Évaluation
Cette issue n'a pas encore été évaluée.