In the "files" pane, we have a search field like this:

It would be great to have the same thing in the "Repositories" pane. I have 1,300 projects in SmartGit, and it since many of the repos are organized into groups, it gets unbearably hard to find a repository sometimes.

SmartGit replaces spaces with underscores when creating a branch name, but not when creating a tag name, remote name, etc. It should just automatically replace in all those fields that don't accept spaces

In some of our repositories we have commits from developers with different Name, but with same email address (short name, full name).

git already supports user name mapping by using a "mailmap" file, so only one name will be display in e.g. the git short log. SmartGit should support this, too.

On GitHub you can assign one or more person to review your pull request. So it would be great to have the same in smartgit. The only thing why I can't use only SmartGit for PRs.

Currently changes in a submodule which is configured with ignore = dirty is shown in Smartgit (7.1.4 #6127, installed: #6097) but not in the command line version of git. Smartgit should respect the ignore = dirty flag and not show these changes.

For instance the following .gitmodules causes the git bash command to ignore any untracked file inside lib/common-libs, but SmartGit still shows the untracked files:

[submodule "lib/common-libs"]
        path = lib/common-libs
        url = git@10.1.2.165:EMS/common-libs.git
        ignore = untracked

With the new Standard window, pull is rejected if working tree contains local changes, error message is:

"The working tree contains local changes.: Commit or stash local changes before pulling."

This behavior is different in log or working tree windows, a pop up allowing to choose some options shows up.

This makes standard window unusable for me.

It should be possible to configure gitea as a hosting provider. 

This would allow to work with pull requests and code reviews. 

GitLab uses git "push options" to allow CI to be skipped for a specific push. We push the same commit to multiple branches and use the git push option when we don't want CI to be run. Putting a CI skip in our commit message would not work because we want CI to run for some of our pushes, and because with our use cases, CI skip would not make sense to have stay in our commit history.

The ability to check a box when I am doing a push to specify that I want to skip CI for that push would be awesome.

I don't care about any other git push options right now, but it might be worth considering that people might come up with new & useful ways to use git push options over time.

Depending on whether you're rebasing (Most do) or merging, the conflict resolution dialog ("yours" vs "theirs") can be impossible to determine unless you manually review the commit id in the log.

For those in the team that aren't programmers it is more or less impossible to understand.

The resolution dialog should be expanded to include far more information. At a minimum one could include the full commit message for the conflicting commits.