When renaming a local branch, it often needs to be pushed to origin under that name and the tracked branch of the local one needs to be set to the new one on origin with that name.

That all needs a lot of clicks and typing in the new branch name by hand. I would propose to extend the Push To window by

- a third bullet point (besides Tracked or matching branch and Custom Ref): "To branch with same name as the one to be pushed"

- another option (besides Force pushing): "Set tracked branch to selected branch on origin (Push To target)"

I hope you'll find a better wording for these points.

Currently, SmartGit only for JIRA supports

- selecting an issue with message as commit message

- marking issues as resolved on push

If you want to have this feature for other issue trackers, please write one reply per issue tracker and vote for that

I would like to be able to quickly view the contents of columns with long strings such as "Relative Directory" by using tooltips. It is difficult to see the contents without widening the column.

In a repository with multiple remotes defined, when trying to Push a new branch created in SmartGit, the selected remote is always origin.

I know that Push To can be used to manually select a different remote, but still it would be useful to be able to specify which remote is to be used as default, and automatically select it if there is no tracked branch configured.

Thanks

I would love if the push to popup had a dropdown with last "custom ref" locations you used. I keep pushing to different branches and it would help a lot having last refs you pushed to as quick selection.

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.