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!
Add rebasing workflow to split up branch into multiple topics
Often i'm working on a long lived branch and I may:
* Need to fix something not directly related to what i'm working on
* Fix something from a previous commit in the same branch
What I often desire is this workflow:
1. Select a range of commits in smartgit
2. Go through each changed file and associate an entire file or hunks within those files to a topic
3. Have smartgit rewrite the history to make each topic a commit
Reveal in Explorer command should be available on all repository regardless of whether it is open
Currently Reveal in Explorer command is only available on open (current) repository.
I don't believe such restriction is necessary and the command should be available on all repositories and only notify/prompt user to remove repository if it can no longer be found.
This should apply to all 'Open in ...' and 'Reveal in ...' commands.
No way to see >1 tag on a commit in Standard Window
When a commit has more than one tag, as far as I can tell, there's no way to see what the tags are. Single tags appear in the log graph, but when there are 2 or more, it just shows "2 tags". Mouse hover, right-click, and select do not show the tags. The only workaround I've found is to open the Log Window and start again. Very frustrating.
The Log Window shows full details in its "Commit" view: branches, tags, on branches, and merged to branches. Very useful. I don't understand why that info is no included in the commit view of the Standard Window. Please add it.
Commit message translation (existing commits)
In the graph window where we see the messages of all commits, it would be really helpful to be able to get a translated version of the commit messages. When you are browsing an external repository it is sometime really difficult to understand a commit when the commit message is written in a language that you don't understand. (I need to work in a Japanese repository and I don't understand any commit messages).
- This should be optional as I don't think that everybody wants to translate everything
- The graph window should display all commit messages in the language of your chosen.
- The commit window when you select a commit should also reflect the translated text.
- You should be able to search for translated text in the filter box component.
- The repository should not be modified with the new translation and allow people to force-push such changes.
- The language of the commit message could be detected automatically (translation services or AI).
I don't know if metadata can be attached to commits but having the translated text attached to it could save time and prevent translating the commit message each time the repository is opened.
Please make SmartGit smart here too: Dialog: Add GitHub Account
Hello
With SmartGit, it’s unfortunately a recurring disappointment that SmartGit doesn’t guide users smartly, for example, this dialog:

- Of course, a user can have multiple GitHub accounts.
- So why doesn’t this dialog explicitly mention which account is being referred to?
Is the user supposed to assume 🥴 that SmartGit is referring to the repository that is currently active?
Well, in reality, a GitLab (not GitHub) repository is active in SnartGit 😉
But that’s true, too, of course:
Thank you so much for this app, which is often smart!
Thanks a lot, kind regards,
Thomas
Bitbucket Cloud integration broken: CHANGE-2770 cross-workspace API sunset (April 14, 2026)
As of April 14, 2026, Bitbucket Cloud has permanently removed the cross-workspace repository listing API (GET /2.0/repositories?role=member&start=0). This was announced in their changelog as CHANGE-2770 and CHANGE-3081.
SmartGit's Bitbucket hosting provider integration still calls this endpoint, which now returns:
CHANGE-2770 – Functionality has been deprecated
This breaks the Bitbucket integration entirely — repository browsing, and any feature that relies on listing the user's repositories. The error occurs regardless of whether SSH or HTTPS is configured for repository access, since the integration layer always uses the REST API.
Affected version: SmartGit 25.1 (latest build as of April 15, 2026)
Steps to reproduce:
- Add a Bitbucket Cloud hosting provider in Preferences > Hosting Providers
- Attempt to browse or list repositories
Expected: Repository list is displayed Actual: Error dialog: "CHANGE-2770 – Functionality has been deprecated"
Bitbucket's replacement API: The new approach requires workspace-scoped calls — GET /2.0/repositories/{workspace} — with workspaces discoverable via GET /2.0/user/permissions/workspaces. See Bitbucket's migration guidance: https://developer.atlassian.com/cloud/bitbucket/changelog/
This affects all SmartGit users with Bitbucket Cloud. Bitbucket Server/Data Center users are not affected.
Please add an option to suppress it the restart popup
in our environment, developer doesn't have admin right to upgrade software. It requires admin right to do it. With that your popup dialog asking to restart become extremely frustrating. please add an option to suppress it.
Scroll long output into view
When command is outputting a lot of lines, scroll the last (current) line in the Output Window into view.
When command has finished, scroll the Output Window back to the top.
Allow passwords to be stored in OS (keychain, hello) instead of encrypted file
Less typing, more secure passwords, and generally a better approach?
Customer support service by UserEcho