Allow repo to be included multiple times in workspaces
Workspaces have been added in the new release 8.2.0.
However, currently it is not supported to include a repository multiple times in a single workspace.
It would be very nice to be able to include a repository multiple times in the same workspace.
A small example on why this is an important feature in many cases:
https://github.com/ThexXTURBOXx/BlockHelper
This is a Minecraft mod of mine which is available for many different Minecraft versions - each of which needing a different workspace to compile and develop it in.
However, instead of dividing the repo into multiple repositories, I decided to create multiple branches in the repository - each of which for a different Minecraft version.
That's why there is a need to include the repo multiple times in the same workspace.
See the attached screenshot for how my GitKraken looks like right now. These could all fit nicely in a single workspace.
Comments: 6
-
12 Aug, '22
Luke HarrisI second this, I'm a game developer who's company has a few games that are different games but are all in the same repository. Would be nice to have them all in a workspace instead of them all being crunched up and illegible in the tab view.
-
15 Aug, '22
dmhudI have a similar use case but with a little extension: add to workspace
repositories from disk or private git-repository with branches (self-hosted server of organization)
USE CASE:
Github repository with many branches, for example: GHRepo
And I clone this repository to the several places on disc. I want use many branches at same time:
/GHRepo_master/.git
/GHRepo_branch1/.git
/GHRepo_branch2/.git
/GHRepo_branch3/.git
/...
And repositories cloned by url from my git-server, which use together with GHRepo:
/from_server/Repo_branch_cfg1/.git
/from_server/Repo_branch_cfg2/.git
/from_server/Repo_branch_cfg3/.git
/from_server/Repo_config_system_for_each_branch/.git
/...
I create Workspace and want add all these folders/repositories/branches to workspace:
- GHRepo_master
- GHRepo_branch1
- GHRepo_branch2
- GHRepo_branch3
- Repo_branch_cfg1
- Repo_branch_cfg2
- Repo_branch_cfg3
- Repo_config_system_for_each_branch -
30 Aug, '22
MikeThe GitKraken UI puts the Workspaces in a highly visible position, which encourages its use, but then, using it highly limits GitKraken functionality because once you start using it, you can no longer have two local repos on different branches of the same remote repo!
There are all sorts of reasons why people would want to have 2+ local repos on different branches of the same remote repo, but those shouldn't matter... just the simple fact that GitKraken is changing the branch of local repos other than the the one that the user explicitly is changing should be enough reason to treat this as a critical defect.
My specific reason for having more than 1 local repo of the same remote repo is because I work on more than 1 release branch. Sometimes I will create a local repo for a feature branch so that I can work on them in parallel. -
31 Aug, '22
MickaelYou work on the next version and you maintain the previous one, you want two work spaces with the same repos in two different versions. One IDE workspace on top of it. This is as simple as that and it concerns many.
-
04 Dec, '22
SergeySometime i need to work in several branches to avoid wasting time.
It will be a lot more usefull if i can see all of instances of one repository in workspace. -
16 Jun, '23
AnikoI second this as well. My team works with repos that run several branches in parallel, on different versions. Rapid switching between branches is not optimal (sometimes it can break things for us), so we store separate branches of the same repo locally.