I have a repo which contains many submodules. If I do some re-organization, e.g. I move a part of the tree to a new location, the submodules contained therein break (i.e. are stated as "missing" for the old location and as "nested root" for the new location). Since this is something I do frequently, its tedious to edit the submodules file by hand to get rid of that.

It would be great if smartgit detects these kind of changes and proposes to update the submodule location entry (moving submodules would then be similar to renames of regular files)

Currently, one can move only one commit within its branch.  Allow to move a consecutive list of commits.

Please add a command line argument that specifies which repositories to open.  This enables scripting groups of repositories to open.  This is needed because it provides an easy way to have repo working groups - SmartGit has a max 50 repos open, regularly closes repos, and does not have an easy "add these repo to the open repos" (it opens only the selected).

Wow, the new standard window looks really great! There's a lot to love here. Nice work!

However, there's one missing feature that currently breaks my workflow: pushing to multiple remotes.

Even though all the remotes display correctly in the UI (like in the history log view), the push button only seems to push to one of the remotes. And I can't find a way to choose which one it is. I found a "Push up to" option in the "Remotes" menu bar, but it's always greyed out. I don't know what conditions are necessary to activate it, and I couldn't figure it out after fiddling with the UI for several minutes. As a result, I can't push to all of my remotes. Just one of them, chosen seemingly arbitrarily.

Ideally, what I'd like is some way to choose which remote to use when pushing, each time I push commits. Some kind of popup to confirm the push and the choice of remote for that push would be nice. The popup UI could even fill out a reasonable default remote for each push, but I'd like the option to explicitly configure that default value as well.

The old (non-standard?) window allows a similar workflow in the "Push to" command, so that's a good fallback for now.

Another way to do it would be to have some place in the UI that lists all the remotes. Then pushing to that remote could be activated from a context menu. That context menu could do other remote-related actions too, like editing. The old (non-standard?) window has something like this in the "Branches" view.

Thanks!

I'm trying to play around with Gerrit. One important missing thing I found is that in typical Gerrit workflow the developers checkout the Gerrit Change, do the changes, amend the commit and push it. For that developers work with detached heads, and pushing looks like this:

git push origin HEAD:refs/for/some-branch

Currently if the HEAD does not belong to any branch it is not possible to even click the Push As... button. If it would be possible to push the button and the appearing prompt would save a history (so I can enter refs/for/my-branch or refs/for/my-other-branch and could select any of them in some dropdown box), it would make the workflow with Gerrit quite functional.

In the current release (22.1.1 #19231) there seem no way to see (or edit) the URL of a remote.

To do that, I must switch to the Log view and right click the remote in the "Branches" pane

Hello,

Thanks for this new standard window, it's really amazing 8)

I was used to work with the Log Window, and I was using main and review alternatives to switch between workflows (working on a local diff or browsing history)

One thing that was really cool about it is that the vertical size of the diff was set independantly

Examples :

Similar as for GitHub, merge requests and their C/I status should be displayed.

Hello,

In SmartGit in the Working Tree Window in the bottom left ist a window labelled with "Branches" which shows a list of local and remote branch names. 

For reviewing I have to search the correct branch for a checkout. As we have several thousands of branches and they are alphabetically sorted within its subfolders, I have to search long lists in each subfolder. It would be sooooo handy to have a search field and filter the branches! Also sometimes I barley remember parts of an old branch name to look up when was or who did worked on a certain feature. I imagine a text filed as it is seen in the Files window.

Thank you

Chris

If I drag and drop the current branch to another one, I get a context menu offering to either reset or rebase.

If I drag and drop a non-current branch to another one though, I only get the reset option; it'd be nice to be able to rebase without having to checkout first.

I understand git rebase may still auto-checkout behind the scene, but even if there is no workaround, it could still be interesting to do it all in one go and come back to the initial context at the end.