Share your ideas on how to improve SmartGit!
This is no support platform! To report bugs or request support, please contact us directly. If in doubt ask us.
First search for a similar request and add your votes or comments there.
Take the time to describe your request as precisely as possible, so users will understand what you want. Please note that we appreciate your time and input, but we don't give any guarantees that a certain feature will be implemented. Usually, a minimum requirement is a sufficient number of votes. Hence, please don't comment like "when will this be implemented", but vote instead.
Follow the stackoverflow.com writing guidelines.
Thank you for your help!
Keyword suggestions for commit messages
Suggestion:
Commit message editor shall make suggestions while you type. Those suggestions would be based on
- Keywords in diffs for current commit
- Filenames affected by current commit
Rationale:
It's quite typical to list affected entity names in commit message. Like, "Moved FooBar global variable from Generic.cpp to Foo.cpp". Having commit message editor suggest those keywords will make writing commit messages easier. I heard TortoiseSVN does that.
Searchable settings
It's really difficult to find setting because you need to browse every tab searching for it. Would be great if it was possible to search like it is implemented in PhpStorm.
Push to several remote repositories
I have several remote repositories bitbacket, github etc. I want to push in each repositories in one click. Now i should to edit the configs manually and push to every repository.
Compare (built-in): improve detection/display of related changes
E.g. denote moved hunks
Please provide samples where SmartGit's compare produces sub-optimal results.
Add the "Stash" action on the popup menu
I am sure you can find some place to add "Stash" somewhere inside this popup menu :-)

Enhance rebase with --update-refs
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://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
Smartgit editor(s) should respect .editorconfig
I can't emphasise how many times per day I fight this issue: I change something in my editor, double-click in Smartgit to see the differences and I realise that tab settings is wrong. So I go to View -> Settings and adjust it. Yet again. Sure, I can save it as default but that works only until I switch to another repository.
How much easier my life would be if Smartgit read .editorconfig (https://editorconfig.org) from given repository!
Add ability for graph squash context menu to work on non-contiguous commits
Add ability for Squash context menu in log view to work for non-consecutive commits. Currently it only works for consecutive commits. If non-consecutive commits are chosen then smartgit would trigger a interactive rebase that does the following:
- reorder selected commits so they are consecutive
- then squash them
If there is an merge issue then smartgit drops into interactive rebase resolve step so use can resolve (or cancel).
Customer support service by UserEcho