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 precise as possible, so we (Syntevo) and other users will understand what you want. A plain request "SmartGit should look cool" is too vague because we don't know what we should change, and hence will not be approved by us.


Thank you for your help!

+28
Completed

Git: Stash selected files [SG-10576]

Marc Strapetz 3 years ago updated by Henrik Heimbuerger 3 years ago 3
Git
+27

Add the ability to successively apply the conflict solver

Chris Jaquet 3 years ago updated by Alexander Zhezherun 3 years ago 3

It often happens during a merge that a number of files in a repository will have conflicts. It is already possible to apply the conflict solver to individual files, but I would like to propose the following workflow:


During a merge when multiple files are conflicted:

  1. Select all the conflicted files.
  2. Choose to activate the Conflict Solver.
  3. For each file in the select list open the conflict solver (as is done for a single file)
  4. User solves conflicts (or decides to cancel), thus terminating the conflict solver for that file.
  5. SmartGit shows a dialogue with the following options "Stage file", "Skip file", "Cancel".
  6. "Stage file" will stage the file and SmartGit will automatically open the conflict solver for the next file in the selected list.
  7. "Skip file" will not stage the file, or mark it as resolved, etc, but will move automatically to the next file in the list, opening the conflict solver for the next file.
  8. "Cancel" will stop the process completely. Files already staged will remain staged.

This will, in my opinion, make merging multiple conflicted files much easier. There could also be a button on the ToolBar which starts the conflict solver for all conflicted files in the current repo, without the user having to select them all.

+26
Completed

Project-level ignore

omegatron 3 years ago updated by Thomas Singer 2 years ago 1

As in this comment


> It would be awesome to have an option "Add To Ignore List" which allows to choose "add to .gitignore" or "add to .git/info/exclude (will be ignored at this computer only)".


When we right-click on a file to ignore it, it should give the option of ignoring it in a .gitignore (that gets committed along with the repo) or .git/info/exclude (which is unique to our computer) or a global gitignore for all repos (garbage files like Thumbs.db. etc)

+25
Completed

Add a "git clean" feature (remove untracked files)

ubruhin 3 years ago updated by Thomas Singer 2 years ago 8

Sometimes one want to clean up the working directory by removing all untracked files, which on the command line is done by the "git clean" command. It would be great to have this feature available in SmartGit.


The most important flags of the "git clean" command may be available as check boxes:

  • -d: Remove untracked directories
  • -x: Also remove ignored files
  • -X: Only remove ignored files

The -f flag (force) may automatically be used(?).


See also https://git-scm.com/docs/git-clean

+25
Completed

Quickly locate/edit Git ignore files

gsimard 3 years ago updated by Marc Strapetz 3 years ago 6

.gitignore, exclude and where the hec is that global Git ignore file again???


Please add a mechanism where the user would be presented with a list of Git ignore file(s) that are in effect for a repository and add the ability to launch an editor against each ignore file.

Git
+24
Completed

Clone: option which branch should be checked out

Marc Strapetz 3 years ago updated by Thomas Singer 3 years ago 3

The Clone wizard should provide an option which branch should be checked out as a result of the clone. This will also affect checked out submodules.

+24
Completed

Git bisect support

Daniel 3 years ago updated by Pierre Goiffon 2 years ago 8

Support of git bisect functionality.

Git
+24
Completed

Advanced multi-worktree support

Marc Strapetz 3 years ago updated by Thomas Singer 7 months ago 12
Git Need More User Input
+23
Completed

Changes view: allow editing file

vseticka.martin 3 years ago updated by Thomas Singer 3 years ago 10

When I review changes that I'm about to commit I often find that I made a typo. I would like to make some adjustments in SmartGit right away to avoid navigating to the file in my IDE.

+23

Changes view: optionally show as unified diff

peradetlic 3 years ago updated by Hannes Schmidt 3 months ago 11

The simplified or "unified" diff view (the default on GitHub for example) is often the preferred way to look at changes, especially on smaller screens