search

nicegram / Nicegram-iOS

Telegram-iOS
542 stars 69 forks source link

### The feature request #184

Closed AcharayuAiyara closed 2 months ago

AcharayuAiyara commented 2 months ago

The feature request

I work in a GitHub Enterprise repository that requires SSH for me (my department) and outside contributors (in other departments). When my contributors fork this repository, I am unable to use GitHub Desktop to push my local changes to these forks. What I discovered is that the remotes that GitHub Desktop creates use the syntax of HTTPS instead of SSH. If I switch to the command line, I can take that branch created by GitHub Desktop (from the fork), and create a new remote that forces SSH instead of HTTPS.

Is this a user setting I'm missing, or should GitHub Desktop be smart enough to know that both the contributor and I are using SSH--not HTTPS?

Proposed solution

Add automatic detection in GitHub Desktop that determines whether the forking contributor is using SSH and then create SSH remotes.

Additional context

Here are some obfuscated examples of the remotes that GitHub Desktop creates on my computer based on a forking contributor using SSH (note the appearance of https):

%git remote -v
github-desktop-afakeusername    https://the_name_of_our_ghe_repo/afakeusername/mybigrepository.git (fetch)
github-desktop-afakeusername    https://the_name_of_our_ghe_repo/afakeusername/mybigrepository.git (push)
origin  git@the_name_of_our_ghe_repo/mybigrepository.git (fetch)
origin  git@the_name_of_our_ghe_repo/mybigrepository.git (push)

Originally posted by @rhetoric101 in https://github.com/desktop/desktop/issues/19074

rhetoric101 commented 2 months ago

@AcharayuAiyara can you tell me why this request was closed? Is this not an issue if GitHub Desktop? Is there a workaround?