I have a top-level folder I use with many many repos cloned in sub-folders.
- Ngôn ngữ chính
- Không có dữ liệu ngôn ngữ
- Star
- 2.1k
- Fork
- 153
- Chỉ số merge pull request
- Không có pull request nào được merge trong 30 ngày
Mô tả
I have a top-level folder I use with many many repos cloned in sub-folders. I need to be able to easily start a new session in that top-level folder. However, now when I do, I get this "Start building across 67 repos" message, with a list of the repos and a drop down defaulting to "main" for each repo (some of them do not have "main"). Then it will pop up a settings menu about worktree settings but I have no idea what it wants me to do. Then take me back to this screen listed all the repos. I just want to continue -- I don't even need to make changes to a single repo right now, I am going to do a prompt that analyzes some code. And the worst part is that my prompt is erased when it goes back to the prompt screen.
Start a new prompt in that top level folder and type:
Hit enter to submit, this comes up
Click Open Worktree Settings ... looks ok to me, what is asking me to do?
Click Retry, my prompt is gone and I am stuck on the same screen:
Not sure how to proceed to be able to open a prompt at a folder that has many sub-folders with different cloned repos. Also, prompt should not be erased when going to these screens and back.
Same issue in 1.1.7
---
| Field | Value |
| --- | --- |
| App version | 1.1.4 |
| OS | macOS 26.5.2 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Week 11 |
Hướng dẫn đóng góp
Hướng nghiên cứu
Start in the /chat flow and reproduce the issue by opening a folder containing many cloned repositories on macOS, then submitting a prompt. Check the transition through the repository and worktree settings screens, including the Retry path. Done means the prompt is retained and a user can start an analysis session without being blocked by unclear worktree setup.
Do mô hình lập chỉ mục viết ra từ nội dung của issue.
Đánh giá
- Công nghệ
- github, macos
- Lĩnh vực
- desktop
- Loại issue
- Lỗi
- Độ khó
- 3/5
- Thời gian dự kiến
- 1-2 ngày
- Mức độ hoạt động
- Sôi nổi
- Độ rõ ràng
- Khá rõ ràng
- Mức phù hợp với người mới
- 55/100