There seem to exist a couple of different ways to bundle desktop applications on Linux - AppImage, Snap, Flatpak, ... Please vote for the below entries, so we can estimate the distributation.

https://github.com/AppImage/AppImageKit/wiki/Similar-projects#comparison

When merging a conflict may occur. The repository is now in a merge state, where a user has different options:

• abort the merge
• solve conflicts and continue

While rebase has a "continue" button, merge has non. Users have to know, that the "continue" button is equal to the "commit" button.

The latest version 19.1 RC2 shows a nice bar:

I suggest:

1. Rename "Commit" to "Continue" in that state.
2. Add a continue button close to the "Abort" button in the merging-state bar.

Thanks,

    Patrick

One of the more annoying and complex issues with Git in general is when merging branches or resolving conflicts - Often the dialog of "Use Ours or Use Theirs" or really unhelpful. Not only is it rarely clear what "ours" and "theirs" is, it can often be reversed depending on the merge/rebase/conflict type.

I think SmartGit could really stand out from the crowd if it put a bit more effort into resolving those words into more meaningful ones. Surely it isn't too much work to determine the name of the 2 branches involved? And if it's the same branch, to display the author and date of the 2 commits in question.

Note: if you are just interested in filtering the Log graph for a specific sub-directory, see topic 879.

As in the working tree window, in the Log it should be possible to invoke commands on directories, too:

• working tree commands (like staging all files in a directory)
• external tools (like opening the terminal for a directory)
• sub-directory logs
• .... what else do you need?

Please post your ideas on how such an integration should look like!

Note, due to several usability and technical reasons, we won't add directories to the Repositories view.

Sometimes I'd like to search the (all, not just the modified ones) files of the commit currently selected in the Log window. This may be useful if a method does not existing any more but you know a state where it existed.

When I select a branch in the Branches tab, Review > Create Pull Request is still grayed out. But it's available in the same menu in the log window. Please enable "Create pull request" for Bitbucket server from the main window.

I can do everything needed to create and prepare the feature branch for the pull request in the main window, but then for the last step as a feature developer I need to open a different window, look for my feature branch again, and finally open the pull request. This is a disruption
in the workflow.
(Reviewing the pull request (fetch, look at commits, comment, approve ;-), merge) is another workflow, usually by a different person - it's okay that this happens in the log window, as we
need the log for that.)

It's easier to read console responses in a fixed width font.

Also, some remotes respond with ascii art that looks terrible in variable width fonts. OK this isn't a major issue, but still...

It would be great if SmartGit could be configured so it doesn’t allow to commit until I fix all of the spelling problems in the commit message.

This way, if I have a typo, it will make sure I noticed it. This, of course, should be optional.

Rebase ("Rebase HEAD to", "Rebase Interactive From") fails because of not stashed changes. It would be great to autostash/unstash files as for Pull-rebase feature.