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!

+1

Missing smart feature: optional automatic background-check: Check all Repositories for changes

Thomas Schittli 12 months ago updated 12 months ago 8

Hello

I miss a smart feature:

If you work in several projects, it is very tedious and time-consuming SmartGit to check in whether there have been changes in one of the repositories: you have to select and check each one manually.

It would be great if you could activate a SmartGit background check for Repositoeries that:

  1. Adjustable e.g. every 60 minutes
  2. Each repository checks whether:
    1. Local changes have been made
    2. There have been changes on the git server
    3. The authentication is still OK
  1. (Annoying Editor: this is 4.)
    The recorded information is then displayed for each repo

Thanks a lot, kind regards,
Thomas

Repository Management
+1

Feature branch commit amend by default

Pierre Durand 12 months ago updated 11 months ago 4

When I work on a feature branch, I always amend a single commit:

- I don't want to have to deal with commit messages each time I push a small change to my feature branch

- In the end, when I merge my feature branch, all commits are squashed to a single one, so the commit messages are lost

Each time I commit, I need to check the "amend" checkbox in the commit dialog.

I would like to have an option "Always amend commit on a feature branch", so this checkbox would always be checked.

It could be turned off by default.

Thank you, I love your product :)

Commit dialog
+1
Completed

Have line spacing options (e.g. 100% 125%, 150%) for code/text, graph, repository, etc. views

Martin Weber 12 months ago updated by Thomas Singer 1 month ago 2

Currently, all the views are tighty packed with text and hard to read. A bit more line spacing might go a long way of making information more readable. Using a slightly smaller font with that still allows for the same amount of information to be on screen.

GUI
+1

Standard window: Expand/collapse merge nodes in all branches view

Bryce Schober 1 year ago updated by Daniel Siegl 1 year ago 1

I just discovered the ability to expand & collapse merge nodes in the "Only current branch" log view, and I love it, thanks!

And now I really wish I had that feature in the "all branches" mode also. Unlike the "only current branch" mode, it would default to expanded as today, but allow merges to be collapsed.

Graph GUI Standard window
+1

Quick Amend and Streamline Single File Commits

Marcelo Filho 1 year ago updated by Thomas Singer 1 year ago 3

Hey SmartGit folks,

I've been thinking about a couple of tweaks that could make SmartGit even smoother for everyday tasks. First off, how about a quick shortcut for amending commits? Right now, we have to tick the "Amend" box in the commit dialog, which is fine but a bit slow if you're doing it a lot. A single keypress or a direct button for this would be super handy.

And for those times when we're just fixing up a single file and want to amend it to the last commit, wouldn't it be cool to have an option to do that without the commit dialog popping up? Like, right-click the file and choose to amend commit directly—using the last commit message as a default. It would streamline those quick amendments.

What do you guys think? Could be some neat quality-of-life improvements, right?

Cheers!

Commit dialog
+1

Find in change-set

Holi 1 year ago 0

Find a text in all changed files of a change-set. In a million+ code lines project some text might appear thousands of times, but you're only interested in the places of files you applied changes to. Add a checkbox to specify that only lines should be found where a change happened.

With that, if you have a huge change-set (e.g. 100+ files), you're able to track down a specific change (that may be problematic) much faster.

Changes view File compare Investigate
+1

LFS prune during Garbadge collector prune

guillaume chauvel 1 year ago updated by Daniel Siegl 1 year ago 1

Add a check box in the garbadge collector popup to be able to fully clean a repository with a single pass on "Local" menu.

or a low level property to run "lfs prune" when the prune checkbox is selected.

+1
Completed

Add ability to squash non-contiguous commits

David Rees 1 year ago updated 11 months ago 4

Add ability for Squash in log view to work for non-consecutive commits. In that case smartgit would run a 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 step so use can resolve (or cancel).

 

Graph Log window Standard window
+1

Commit: word completion should also suggest current branch name

Duoc Dam 1 year ago updated by Thomas Singer 1 year ago 0
I want to suggest a feature that will auto-copy the branch name into the commit message textbox because I often work with multiple branches and each commit message should start with the branch name.

This feature is the same as a function of the GitToolbox plugin for IntelliJ

Image 836

Thanks and regards!

Commit dialog Improve Git commands
+1

Finish Feature dialog: explicitly name target branch

Neo 1 year ago updated by Thomas Singer 1 year ago 0

With github calling new master branches "main", the application is a bit confusing when setting up the feature branch flow option as it asks for "main branches".

Further more and even more confusing, when you come to finishing a feature, on the Finish Feature dialog, the first radio option is "Finish to main branch". This should state the name of the branch selected at feature setup as "main" is now confusing.

In my case I'm using the "develop" branch for all developments and "main" for production in line with Git-Flow process. As you can imagine being told each time that I'm finishing to "main branch", when in reality I'm finishing the "develop branch" (even though this does happen behind the scenes) is a bit disconcerting. I appreciate the text sub text at the top of dialog states the "develop" branch, but at quick glance it would be better if the radio also showed this.

If would be ideal at setup to request "derived branch(es)" rather than "main branches" or something similar, and then on the Finish Flow dialog, show the branch name you selected at setup that you are actually finishing to.

Thanks.

Image 831

GUI