The GitHub workflow is described in the Kubernetes contributors documentation.

In practice we want that, if a user starts a workspace

• from a repo (the upstream) for which he has a fork (the origin)
  Or
• from a repo (the origin) that is a fork of another repo (the upstream)
  the git remotes should be setup automatically. For example:

$ git remote -v
origin	        https://github.com/eclipse-che/che-docs.git (fetch)
origin	        https://github.com/eclipse-che/che-docs.git (push)
upstream	https://github.com/eclipse-che/che-docs.git (fetch)
upstream	https://github.com/eclipse-che/che-docs.git (push)

This can currently be achieved if the DevWorkspace has the following projects:

projects:   - name: che-docs
    git:       remotes:         upstream: https://github.com/eclipse-che/che-docs.git
        origin: https://github.com/amisevsk/che-docs.git
      checkoutFrom:         remote: upstream
        revision: main

A possible solution is to:

• Add a new URL parameter (remotes):

  # 1. explicit name and URL
  ?remotes={{origin,https://github...},{upstream,https://github...},...}
  
  # 2. URLs only, name is implicit: first is origin, second is upstream, subsequent are fork1, fork2 etc... 
  ?remotes={https://github...,https://github...,...}
  

• Implement a Chrome or Firefox extension that does add the remote parameter automatically

Another solution is let the dashboard figure this out during the generation of the DevWorkspace object.

Upstream links:

• It should be easier to configure remotes in Devfile v2 flow
• Che factory chrome/firefox extension