At the moment (version 23.1 preview 10) it is possible from the Working Tree window to visualize changes from submodules (can be enabled with Ctrl+7) and to commit them in different repositories (super and submodules) at once. This correctly produces commits in multiple repositories with only one UI dialog interaction.

What I believe is missing from this feature is that the submodule pointer changes are not committed in the superproject.

What is the point in making multiple commits at once if later I need to make another commit in the superproject to update the submodule pointers?

It would be nice if the [Commit] window would display commit messages in Markdown. 

Even if it's an opt-in advanced option, I would be happy.

The list in “My History” should to be sortable by date. I mean, how can it be “my history” when it doesn’t show at the top what I’ve done most recently?

Also, being able to filter would be useful.

Actually it's just about providing the same functionality for "My History" as it is provided for "All Branches + Tags":

With version 23.1, SmartGit has replaced the built-in dialog to create a Pull Request by re-directing the user to an appropriate URL for the respective platform. We see following advantages here:

- the amount of clicks required to create a Pull Request stays the same

- all options are available which the specific platform offers; by design, SmartGit will never lag behind

We need your input here!

Up-vote this issue if you still prefer to create Pull Requests directly from a built-in dialog in SmartGit, even if it lacks specific options. In this case, comment on why you prefer the built-in dialog/which advantages this has or upvote appropriate existing comments.

Down-vote this issue if you agree with the mentioned advantages and comment on possible other advantages of the re-direct.

For version 23.1, the former built-in dialogs can still be enabled using the appropriate Low-Level-Properties. These are declared as Experimental to denote that we might drop them in a later version for technical reasons (e.g. if APIs are changed or they raise other technical issues). The more votes this issue has, the more effort we will spend into preserving them.

log.azure.createPullRequestOverAPI
log.bitbucket.createPullRequestOverAPI
log.github.createPullRequestOverAPI
log.gitlab.createMergeRequestOverAPI

I'm working with a big project with multiple contributors and several dozen branches. At times I need to figure out where a specific branch came from, and how it relates to the other branches, but it's hard when I'm scrolling, scrolling, scrolling to get past all the individual commits.

Suggestion: have a way of collapsing the graph display vertically, so that I can see more of the structure without scrolling. Some possibilities:

• If a range of commits are selected, then right-click to show a "Collapse" item, which collapses the commits into a single line (still showing the vertical colored lines) with a button to un-collapse

• Have a "Collapse everything" button which collapses all commits which aren't merges or branches

Another possibility: have a (floating?) "Graph Overview" window which gives you a compressed overview of the graph. Selecting items on the floating window would select them on the main window, and vice versa.

There is an option in Gitlab to enable Delete source branch by default for newly created merge requests.

But it gets enabled for merge requests created only in a browser.

If I create Merge request in SmartGit I always get this option disabled.

It would be great if the default setting was used when creating merge request in SmartGit and also an option to enable or disable it in Merge Merge request window.

A classic problem in large repositories is when someone reformats the code, touching most lines in every file. This makes git blame a lot less useful, as all roads lead to Rome (the revision where the reformatting was done).

git blame, however, can ignore a list of revisions:

> git blame --ignore-revs-file .git-blame-ignore-revs

Adding this to SmartGit's Blame and Investigate views would be very handy.

Currently, we can't change the author of a merge-commit, but it is possible via `git commit --amend --author=xxx`

The older topic only works for commits having the same message.

I quite often need to squash 2 commits that are not consecutive and which have different messages. But, currently, only the rebase option is presented.

This could work for consecutive commits too, as a shorthand for the right click > squash option.

My regular multi-repo need is branch manipulation across many repos - checkout, add, delete, and rename.  Currently, I use an IDE or create scripts to do so for products' source I'm working on.  I think the best multi-repo-git-client, SmartGit, should have these features so users can stay using it instead of switching tools.