Bug
When dual create <name> is run, the new workspace instance has its git origin remote set to the root folder the project was branched from (the local path) instead of the real remote origin (e.g. the GitHub URL).
Expected behavior
The new workspace clone should have origin pointing to the actual remote URL (e.g. git@github.com:org/repo.git), not the local filesystem path it was cloned from.
Impact
This breaks push/pull operations in the new workspace since the origin points to a local directory rather than the upstream remote.
Bug
When
dual create <name>is run, the new workspace instance has its gitoriginremote set to the root folder the project was branched from (the local path) instead of the real remote origin (e.g. the GitHub URL).Expected behavior
The new workspace clone should have
originpointing to the actual remote URL (e.g.git@github.com:org/repo.git), not the local filesystem path it was cloned from.Impact
This breaks push/pull operations in the new workspace since the origin points to a local directory rather than the upstream remote.