See the animation https://www.gitkraken.com/learn/git/git-rebase#how-to-git-rebase-with-gitkraken-client https://www.gitkraken.com/learn/git/git-rebase#how-to-g

See the animation https://www.gitkraken.com/learn/git/git-rebase#how-to-git-rebase-with-gitkraken-client https://www.gitkraken.com/learn/git/git-rebase#how-to-git-re... . It is very limited as I said (happens at the branch level not individual commits and you can't choose base), but at least it solves one of the most annoying (but solvable) parts for me - remembering which of the 3 arguments for "git rebase" is which and in what order they go. Even in GUI clients where you have single "rebase" button interacting with current branch it's not always fully obvious whether it will rebase current branch or on top of current branch. Of course it's not hard to imagine how a program could potentially do a lot more. And I would understand if compared to that you called the functionality GitKraken provides as having nothing at all.