Upstream Already Exists SSH => HTTPS
- Dominant language
- TypeScript
- Stars
- 21.8k
- Forks
- 10.5k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 25
Description
### Describe the bug
When I have a Fork I can also write to, I get the upstream already exists pop up. Because GitHub Enterprise, I use and SSH key. The upstream workflow seems to want to "downgrade" my forks to HTTPS.
### Version & OS
2.3.2-beta8 - Windows 10
### Steps to reproduce the behavior
1. Have a fork checked out via SSH.
### Expected behavior
It would switch upstreams without switching protocols.
### Actual behavior
It switches protocols.
### Screenshots
Contributor guide
Research direction
Reproduce the upstream-already-exists workflow with a fork checked out via SSH on Windows 10, as described in the issue. Trace the workflow that updates the upstream remote and verify that the completed change preserves the existing SSH protocol instead of switching it to HTTPS.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- electron, git, typescript
- Domain
- desktop, developer-experience
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100