Some git flow operations (hotfix finish, release finish) push master and dev branches to origin, but Finish feature does not. I found myself self several time having not pushed dev branch as I expected Finish feature will do all steps required.

If i had one commit unpushed i wanted to see it down below in the outgoing section. The problem here is that there is no option here to filter only the unpushed items.

Right now when you compare changes in two panel diff tool, or three panel diff tool you can got case when diff tool allows you only to replace code. It can happen when in two branches the same line of code has been changed and you are trying to merge these files.

It would be great to have possibility to force diff tool to insert diff line if SHIFT key is pressed.

TortoiseGit provides a Revision Graph. This provides a quick overview of the existing branches (local and remote/remotes). From this overview, logs for specific branches/tags can be opened and it is very easy to switch.

Especially for new Git users this overview can be very helpful.

It would be nice to add something like this to SmartGit.

The manual and its features can be found here:

https://tortoisegit.org/docs/tortoisegit/tgit-dug-revgraph.html

When switching to/from a branch where new files are added sometimes files are left behind (soapui project xml for example), when switching back to the branch with the new files you'll often get the warning "The following untracked working tree files would be overwritten by checkout", and a list.

It would be nice to have an option added to this dialog to basically say "ok, overwrite them". Instead of having to look them up 1 by 1, and manually deleting them before trying to switch to the branch a second time.

Hello,

Summary : introduce ability to perform rebase with --update-ref, and enhance UI around it

Use case solved :
- you work on a big feature, and you have to split your work into multiple PRs. You have therefore many branches and Pull requests based on each other (also called chained PR, PR trains).
- You are working with a git flow where you occasionally need to rebase/squash/force-push to integrate fixes in your feature branches before merging them

The problem : Suppose you need to fix a bug on the very first branch with a rebase on the original commit, you'd have to also rebase all other branches. --update-ref allows to do this once

Additional enhancements possible : the smartgit UI could tell you which other branches had their refs updated, and suggest to push them as well. It is unsure if this is always the desired behavior (for example If you are working with a teammate on this PR-train, and you need to better co-ordinate) 

Original message : 

I just discovered this feature from git called --update ref released actually a couple years ago in 2022

https://github.blog/open-source/git/highlights-from-git-2-38/#rebase-dependent-branches-with-update-refs

https://medium.com/@bruce.ho98/a-better-way-to-rebase-stacked-prs-aa9b4dc600f1

I was wondering if this is something that could be introduced to Smartgit ? It could be either silently (just applying the parameter) or even better, having some UI feedback about the list of other updated branches, along with support regarding pushing all those branches.

It could be a killer feature for teams committed to making small PRs and often needing to cascade them.

Notes : there are some tools that seem to provide similar behavior to rebase --update-refs available online like https://github.com/realyze/pr-train

Best,

Cyril

It would be really helpful to me if there were a simpler way to check out PRs and/or their branches to a worktree subdir of the current clone. IMO, this would be most discoverable as a right-click option nest to "Check Out...", as in "Check Out to new Worktree...". This right-click option could be made available on any branch selection, or even any commit selection context where "Check Out..." is offered.

Similar to `git diff <hash1> <hash2>` I want to select the first commit by searching in the log, mark it as "selected", then search the second commit, select it and do a compare. Alternatively, if a commit is selected, any commit can be clicked on to do "compare with selected". BeyondCompare has a similar behavior when selecting files from the Explorer.