MultiRepo management

[yindf]

In our project, we have many repositories, and using tabs to switch between them is not as efficient as expected. Therefore, a tree view was added to show the repository hierarchy and state, which is called a repo group like this:

how about to add function like this?
pls take a look at Rider's git tools, when multirepo management is needed, it's almost the best choose.

[love-linger]

1. SourceGit supports group repositories in welcome page
   
2. SourceGit supports Workspace. You can create multiple workspaces, the SourceGit can remember the repositories you have opened in that workspace. It is the fastest way to switch between multiple repos.
   

[yindf]

Thank you for your quick response!

Of course, I know that feature. I have used Fork for years, but when we have more than 10 repositories, the tabs become too small to show the repository names clearly.

It's difficult to manage a repository without a clear hierarchy, especially as our repository is expected to grow to about 40 repositories. For our scenario, it is important to have:

A button to pull all repositories together.
A clear display of the hierarchy.
A clear indication of the state of each repository.
The ability to show changes across all repositories, stage, and commit them together.
The ability to push the commit to the remote repository together.

All these functions have been implemented in my fork, and we have been using it for a while, which has helped a lot. If you consider adding this kind of functionality, I can clean up my code and make a pull request.

[yindf]

By the way, in the tab, the fork shows a dot to indicate changes in the repository, but SourceGit has lost this ability.

[love-linger]

By the way, in the tab, the fork shows a dot to indicate changes in the repository, but SourceGit has lost this ability.

I do not really like this design. The local changes is NOT like file changes in common text editors, which will remind user that something has not been saved. But for local changes, what is the same thing as Has not been saved as files? Or if user want to close this app directly, should we prompt them with You can some local changes that has not been committed or pushed?

In another word, when there are some local changes, what we want user to do?

[yindf]

// We use this to show that the repository has 2 local changes and is up to date
// 4 commits behind, and has 3 local changes

However, if these are added to the tab, it will make the tab too long.

[yindf]

I realize that a dot alone is not enough, so we add other indicators to show the status of the repository. This is clearer than using just a dot.