[Bug]: the name of forks are the same title as the upstream repo
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 23k
- Forks
- 5.9k
- Avg merge
- 11h 14m
- Merged PRs (30d)
- 357
Description
Before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to reproduce or investigate the problem.
Area
apps/desktop
Steps to reproduce
- fork a repo and rename it something
- try to open both repos and the fork in t3code
Expected behavior
t3code will show the fork name different from the upstream repo
Actual behavior
t3code will call both the repo and its fork by the same name, making it hard to see if you are working on a fork or the actual repo
Impact
Blocks work completely
Version or commit
latest nightly ( T3 Code Nightly 0.0.32-nightly.20260729.951 (a8e05cbb9263) T3 Code Nightly 0.0.32-nightly.20260729.951 (a8e05cbb9263) Pre-release)
Environment
Fedora 44
Logs or stack traces
Screenshots, recordings, or supporting files
No response
Workaround
settings -> project grouping turn that off (thanks @Baker)
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
Start in apps/desktop and reproduce the issue with an upstream repository and a renamed fork open together in t3code. Read the project grouping setting and the code that derives repository display names. Done means the fork and upstream repository are shown with distinct names while project grouping remains enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, typescript
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100