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

[Sy-D]

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

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

[juliusmarminge]

how do you envision this working? we clone with generic git clone so the global git credentials must have access to what you're tryign to clone

[Sy-D]

@juliusmarminge Thanks for the clarification.

My setup is that I have multiple Git credentials configured: my global/default credentials are for my work GitLab account, while the repo I’m trying to clone is a private GitHub repo.

A couple of questions from my side:

1. Do the source control connectors provide authentication for cloning, or is cloning always done purely through the globally configured Git credentials?
2. If the connectors do provide authentication, would it make sense to try the enabled connectors when multiple source control providers are configured?
3. If cloning only uses the global Git credentials, would it be possible to make the default provider/credentials configurable per project or workspace?

I tried disabling the work/GitLab provider so only my personal GitHub credentials would be used, but that setting appears to be locked in my t3 code.

So this might be either a bug/UX issue, or a feature request: for users with both work and personal Git accounts, it would be helpful to have more control over which Git provider/credentials are used for cloning in a given project. What might be neat, maybe i am wrong is to attach lets say git credentials 1 to group x and credentials 2 to group y. Otherwise i would go back and setup different credentials based on the work dir in the global .gitconfig file but that would still not fix that issue with the cloning

[jonsing]

@Sy-D Quick thought.. I have a similar setup (but not GitLab) as you do when it comes to Git. Have you tried using .gitconfigs?

This is the best resource I have that describes the setup I'm referencing: https://www.redeploy.com/post/setting-up-multiple-github-accounts-with-custom-config

Might work, might not.. :)