In a multi-repo workspace, when given full urls of specific branches of the modules, origin is always set to origin/main

[srgwsrgwetgethg]

Bug description

In a multi-repo workspace, when given full urls of specific branches of the modules, origin is always set to origin/main
Also, the git module shows as active branch the branch of the main repository.
To must do a git switch to activate the desired branch.

Steps to reproduce

• Create two repos (in bitbucket) (e.g. main and module)
• Create a branch for each repo (eg v1 and v1.0)
• Create a workspace for for ../main/src/v1 (the full branch url)
• add a additionalRepositories entry for module/src/v1.0 (full branch url)
• add a main.code-workspace file to add a workspace folder for the module repo.
• create a prebuild for this configuration
• create a new workspace based on the prebuild

Now the Source Control plugin will show the module folder as if it is pointing to branch v1 (which does not exist) and actually git will push to the main branch of module.

Workspace affected

No response

Expected behavior

Just as with the main repository, the 'origin' of the module should point to the branch used as url in the additionalRepositories configuration.

Example repository

No response

Anything else?

No response