Microsoft/vscode

GitHub - can't fork a fork

Open

#160,377 opened on Sep 8, 2022

View on GitHub
 (0 comments) (0 reactions) (1 assignee)TypeScript (74,848 stars) (10,221 forks)batch import
buggithubhelp wanted

Description

  • Open my codespace which is on https://github.com/mdehling/stable-diffusion
  • Try to push a commit on the notebook branch (is there a command to fork manually because I didn't remember that I have to try to push to get the fork prompt to show up?)
  • Get an error:

Because upstream was already set to the real upstream

$ git remote -v
origin  https://github.com/mdehling/stable-diffusion (fetch)
origin  https://github.com/mdehling/stable-diffusion (push)
upstream        https://github.com/joaomoreno/stable-diffusion.git (fetch)
upstream        https://github.com/joaomoreno/stable-diffusion.git (push)

Contributor guide

Tech stack
typescript
Domain
developer experiencetooling
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
basic git knowledgevscode git integration
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
The issue reports that when attempting to push from a codespace on a fork (mdehling/stable diffusion), the fork prompt does not appear because the upstream remote is already set to the original repo. The expected behavior is that the user should be prompted to fork the repository when they lack write access. Investigate the VS Code git extension's fork detection logic, specifically the code that determines whether to show a fork prompt. Look at files like `src/vs/workbench/contrib/git/browser/gitWorkbench.ts` or the GitHub Pull Requests extension. The fix may involve checking if the remote is already a fork or handling the case where remotes are pre configured.