Often, we have to switch between various git repositories, many of which can be collated under a single workspace-like structure. for this, it is required that the Project/Workspace feature be provided as feature as it is present in Sublime Text.
Preferred solution
Say one keeps juggling between the repositories created for various organizations or clients or OSS projects. This person has a hard time maintaining the tabs and the credentials associated with various repositories. So, I recommend that Projects and Workspaces feature be ported to Sublime Merge along with a credentials vault as defined at https://github.com/sublimehq/sublime_merge/issues/1816
This way, if I have to work on several repositories that belong to different projects, I could create workspaces for every project and the relevant repositories there. As the projects would also have a creds vault (see: https://github.com/sublimehq/sublime_merge/issues/1816), I could always choose which credential to use.
Problem description
Often, we have to switch between various git repositories, many of which can be collated under a single workspace-like structure. for this, it is required that the Project/Workspace feature be provided as feature as it is present in Sublime Text.
Preferred solution
Say one keeps juggling between the repositories created for various organizations or clients or OSS projects. This person has a hard time maintaining the tabs and the credentials associated with various repositories. So, I recommend that Projects and Workspaces feature be ported to Sublime Merge along with a credentials vault as defined at https://github.com/sublimehq/sublime_merge/issues/1816
This way, if I have to work on several repositories that belong to different projects, I could create workspaces for every project and the relevant repositories there. As the projects would also have a
creds vault(see: https://github.com/sublimehq/sublime_merge/issues/1816), I could always choose which credential to use.