I asked if we could open files from the log, but that's apparently not possible because they might have been moved since that commit, etc. we can only copy "relative path".

Then I thought I could sort by "Last Changed On", but that's the filesystem modification date, not the last time it was changed in the git history. If you check out a different branch, all files changed in that branch are marked with the current datestamp, rather than the last time they were modified in the history.

If you could show the last time they were modified as a column in the Files view, that would work.

Hello guys. 

I have been using SmartGit for years. The longer I use it the more I love it. But also I am getting used to click 'commit and push' button pretty quickly and automatically. Keeping in mind that I shouldn't do that and that I have to verify my commits before pushing, I cannot stop. 

So I ask you to add an option to disable or even hide this button. I would be happy to free-willy disable it which would force me to split the process into two steps: commit, then push. 

Hope to see this feature soon since it's not so hard to implement and also it's not a big impact for the ones who disagree. 

Currently, when investigating a file (right click file/investigate), the Diff view :

only shows the diff between the selected file (New contents) and the previous version (Old contents).

It would be nice(r) if it was possible to select a previous version in the Navigation pane e.g:

and have that replace the Old contents so one could compare (i.e. not unlike the functionality from using the working tree view and doing it there - just focused more in the Investigate window as then one is looking at the one file rather than the whole commit)

It would be useful to see a name of the branch we're going to force-push.

When opening the file-specific log view and selecting two commits to show the diff, all the files modified between these two commits are shown. Since the intent is to look at the initially selected file, it would be much better if the filename was set by default in the filter, or maybe have an option to only show the logged file which would work across file renames.

When a repo's master branch has incoming changes and the repo is checked out to master, SmartGit displays the helpful down arrow indicator. But, if the repo is checked out to a non-master branch, there is no indicator for the branch-to-master status (as the indicators are for the checked out branch). To learn if a repo's master branch has incoming changes to update and rebase my working branch on, I have to click on each repo to review it. This requires reviewing the graph to find those commits and see how they align - is the branch missing commits from master.

The current product I'm working on has over 20 repos. To help this, perhaps an indicator on a branch in the Branches view when the branch is behind on its master branch?

Hello,

I'd like to see in SmartGit the following additional options when we right-click (i.e. in windows) over a folder in the "Local Repositories" window:

- Open all repositories of the folder, keeping the current opened repositories intact. (i.e. option: "Open all, keep current tabs...")

- Open all repositories of the folder, replacing (closing all) the current opened repositories. (i.e. option: "Open all, replace tabs...")

The reason I think this feature is very important, is because we may use the SmartGit for multiple groups of repositories like i.e.:

- Different work projects (multiple groups of one to many repositories per project)

- Different personal projects (multiple groups of one to many repositories per project)

Having in mind that the "Local Repositories" window aids to organize our repositories in a hierarchical way under user-defined Folders, it would be great to have the option to right click on a folder and be able to select if we want to open all the repositories it contains at once, by just opening them and appending to already opened repositories we have in our tabs, or by firstly closing all the currently opened repositories that we have.

It seems like a simple addition to SmartGit, with two more options in "Local Repositories", which give us the new ability in organizing our groups (Folders) of repositories in "workspaces". Thus if I want to open my work's repositories of project #1, I just right click on the folder "Work/Project#1" and select "Open all, replace tabs..." and voila I have a "workspace" of opened repositories for this specific project. Otherwise we have to close and open manually multiple repositories..

Additionally it would be also necessary, when we open the folder's repositories, the order that we have set in the repositories tabs (Standard Window) in the past, to remain the same, and any new repositories in the folder to be added in the end. That would enhance the semantic idea of "workspaces".

Please think about it. I've seen similar utility in file-handling software, where you can store and restore the tabs of the folders you have set for the different projects. And I feel that SmartGit has already the underlying mechanisms ("Local Repositories" and folders) to support easily such a new functionality.

Thanks

When creating a branch in the Standard window for which a remote branch already exists, it currently is rejected to better check out the remote branch. However, sometimes this would cause problems, e.g. in combination with submodule or LFS changes. Hence it would be better to allow the creation of the branch at the specified commit, but configure the tracking for the remote branch.

Add "Unstage Hunk" to (right) Index panel when comparing HEAD vs. Index (in context menu/hotkey).

Now it is only available in left pane.
It should do the same action as "Unstage Hunk" in left pane currently.

There is a common workflow to have some big feature branch with every small ticket having it's own small branch.

Small tickets get merged into the feature branch in some way, the way isn't related to the request.

As an author of some ticket branch you want to keep up with the feature branch.

For merges of other ticket branches, it's the old plain rebase/merge.

But time has come to rebase the feature branch onto a fresh develop/main/master/... version.

Somebody performs the rebase and solves all the conflicts.

Then you have to rebase your branch onto it and here is the pain: you have to solve all the conflicts solved in the original feature branch again.

My proposal is to add an option to simplify this: when some old commit in your branch (b1) is pointed by a local branch (b2-loc) which is diverged from it's tracked branch (b2-rem) and you rebase your branch (b1) onto a commit pointed by the diverged remote (b2-rem), add an option to "rebase only your changes".

The simplest way this option can work is to create a temporary branch on b1, hard reset b1 onto b2-rem, cherry-pick every commit from the temp branch into the new b1, starting from the one which has b2-loc as a parent, delete the temporary branch.

I personally perform this routine pretty often and I would like to have an option to do this in a single click.

When I do so, it's also inconvenient to solve conflicts your changes have with b2-rem, because mass cherry-pick breaks on conflict and you have to search for the conflicted commit from your changes and select every commit after to continue your cherry-pick, repeat on every conflict.