pingdotgg / pingdotgg/t3code

[Bug]: Adding private personal github repository doesnt work due to git clone issue

Open
#3,664 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug needs-triage
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
  1. In the left sidebar click add project.
  2. Go to the Github repository.
  3. Paste the url of the private repository.
  4. Clone it

Other workaround which i tried is to create a empty destination folder to clone it into which didnt work too

My global git user is a different one than the one i authenticated myself inside the application under source control providers which is my private one and has access to the private repo.

Expected behavior

Cloning into the destination works with the current authenticated user under source control providers of the app

Actual behavior
Image
Impact

Major degradation or frequent failure

Version or commit

0.0.28

Environment

macOS 26.3

Logs or stack traces

Screenshots, recordings, or supporting files

Bildschirmfoto 2026-07-02 um 22.18.54.png

Workaround

cloning it via cli and adding the folder afterwards

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in the apps/desktop add-project flow and reproduce cloning a private GitHub repository while the app's authenticated provider account differs from the global Git user. Trace how source control authentication is passed to the clone operation. Done means the private repository clones into the selected destination using the app-authenticated account; verify the existing CLI workaround is no longer needed.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, github, typescript
Domain
authentication, desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.