I opened a new GitHub repo, and its "New Session" was cloning the repo (as ex...
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 157
- PR merge metrics
- No merged PRs in 30d
Description
I opened a new GitHub repo, and its "New Session" was cloning the repo (as expected) - while in this state I used teh Categorize feature to give the project a yellow color and it showed correctly in the UI. I also moved the project to the end of the list.
After a while it finished cloning the repo at which point it moved the project to the beginnign of the list (wrong) and forgot its color (also wrong).
| Field | Value |
|---|---|
| App version | 1.1.15 |
| OS | macOS 26.6.2 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Day 2 (Week 1) |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the flow in the desktop app at /chat: create a new GitHub repository session, apply a yellow category, move it to the end, and wait for cloning to finish. Trace where cloning completion updates the project list, then verify that the project remains at the end with its yellow color preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, macos
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100