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 users will understand what you want.


Follow the stackoverflow.com writing guidelines.

Thank you for your help!

+1

Highlight matches in text with yellow color when filtering by "Content"

Anton 7 months ago 0

Image 794

Image 795

File compare GUI
+1

Standard Window, Repository Tabs : double click to close

terablade2001 7 months ago updated by Thomas Singer 6 months ago 2

Hi.

Having catch myself multiple times doing double click on the repositories tabs in the standard window in order to close them (driven by the behavior on other S/Ws with tabs that I am familiar with) but with nothing happening, I'd like to ask for this feature.

Thus the idea is: "Double Click" on a repository tab = "right click + Close" over the tab.

Thanks

Standard window GUI
+1

Tags first-priority in commits rows and different coloring

terablade2001 8 months ago updated 7 months ago 4

Hi.


Recently I made some work with tags in my workflow using SmartGit. To be honest, I found it hard to recognize them among many commits. Then I though to propose a feature : to permit users to set specific color for tags (i.e. I am using yellow color to be identified easily). And also providing an option to place tags first per row.

Then I tried to make an example for you to see what I mean. In the next figure, in left side, please find the tags (supposing you don't know them, or remember them). It's visually relative hard to find them, even in just 7 rows with just a few text (mostly because their color is similar to the remote branches). Imagine what happens in cases of more lines with much text per commit or multiple remotes.

Then I opened the test with another common program I use till now (where user can also set colors for different things).


Thus notice that Tags are yellow (and not gray as remote branches) and they are placed first (not last - depending on the remotes and the branches they may not be also visible due to lines length!). This placement (the second) gives priority on tags, both visually and by position, making them visible at a glance and ensuring they are always visible.

I can only imagine how the SmartGit view could be with the tags in frond with yellow/black background/foreground, and I have the impression this would be a better approach than it's now (but maybe I am biased due to by relative experience with such S/W).

Thus my proposal for enhancement regarding view of tags is:

1. Permit user to decide if he wants then at the start of each row, or at the end (as it's now)

2. Provide user the option to give color (background/foreground) to the tags.

Thanks

Image 792

Graph
+1

Improve handling of incoming changes for files marked as skip-worktree or assume-unchanged

Blake Campbell 8 months ago updated by Thomas Singer 8 months ago 1

See also: https://smartgit.userecho.com/communities/1/topics/422-automatic-override-of-files-marked-with-skip-worktree-during-pull

If I have some files marked as skip-worktree in my index and I want to pull down changes from the remote, I will often have to manually stash, pull, then re-apply my stash. It would be helpful if, instead of just failing with an error due to having skip-worktree files in the index, SmartGit would offer to attempt to automatically stash and re-apply the stash for you. Obviously if there are any conflicts that would have to be dealt with, but it would save a few clicks in most situations for me.

For context: I often find myself making changes to checked in configuration files for my local environment which I do not want to commit to the repo, so I will mark them as skip-worktree so that I don't run the risk of accidentally committing/pushing my changes to those files.

+1

Standard Window: assign colors to repositories (colored tabs)

terablade2001 8 months ago updated by Thomas Singer 6 months ago 2

In the Standard Window there is a top row where each opened repository is represented by a tab. Currently I work with at least 6 tabs opened. Some of them are grouped to some specific parts of my project. Thus I would like to have a way to easily/faster discriminate among them depending on what I want to do. Ordering is one way. Also some of them may left with non-staged files because I need to focus on other repositories or complete tests. Other may be related with high/low priority issues. Thus I would like a fast way to annotate them i.e. by their category or status, and this way is via custom coloring.

As I am thinking it, there should be a color palette in preferences where user can have a predefined set of colors (for light and dark theme correspondingly for optimal-view purposes) and also be able to create his own custom colors. Then to easily right click on any repository tab and select the background and foreground(letters) color he wants for each tab, via a pop-up color-picker window. As far as the repository tab stays open, in different sessions, the color should remain. If closed should be reset to default colors the next time is opened. (Or this could be a preference if someone wants the tab colors to be retained after closing a repo, and reloaded after opening it again).

This is a feature, which I have seen in other apps I work with, like MobaXTerm when opening multiple terminals (if anyone wants to get an idea).

GUI Standard window
+1
Completed

Add a stage-changed (stage-all) command in Standard Window to stage all files at once

terablade2001 8 months ago updated by Marc Strapetz 8 months ago 7

Hi.

Coming from other git handlers (i.e. like git-gui, etc) I can't find a 'stage-changed' command in order to automatically stage all the changed files in the Standard Window. One solution is to select all files and press the stage button. I also noticed that in Worktree window, the stage button opens a pop-up window to select which files to stage, by having as default all files selected. Thus there are workarounds. But, in the Standard Window, a simple button to stage all changes would be really useful.

Unless you have this functionality already - and I don't see it - please add it! There is no reason to stage one-by-one the files as a default behavior. The default behavior I think is to stage all files, unless we have a reason to stage specific files. And there is no reason to open second window (which we may need to close afterwards) just for a stage-all case.

Thanks!

+1
Completed

Add option to remember last size, customize default size of dialogs like Save File As or auto extend

L Nguyen Huu 8 months ago updated by Thomas Singer 8 months ago 1

Issue: the Save File As (Ctrl+S on file in diff view) window popup is too small to read long paths:

Image 781

I need to either click inside the text field and move to the left word by word with Ctrl+Left, or resize it to see more text:

Image 782

However, this new size is forgotten next time I Save File As.

A. It would be nice if last popup size was remembered. Or, if not everyone wants this, at least add a Preference option to remember last popup size.

B. Alternatively, there could be a numerical option to specifically set Save File As popup width.

C. Alternatively, there could be an option to auto-extend the popup size to show the full path text (to the limit of the monitor width)

+1

Azure DevOps: add support for pull_request_template.md

anthony 8 months ago updated by Marc Strapetz 8 months ago 0

we are using pull_request_template.md files.  when creating a pull request, if this file is present, the PR should include this content

I wanted to update this with a link:

Improve pull request descriptions with pull request templates - Azure Repos | Microsoft Learn

I see there is a similar request. here:
Support GitHub PR Templates / General / SmartGit (userecho.com)

The templates are in different files, but the 'ask' is probably the same. I should point this feature is extremely important for companies that have compliance / ISO workflows... The create PR feature from within smart git is not very useful if you have to 'copy paste' the template after the PR is made.

Hosting provider
+1

Branch's name in Title of Main window

shaidarov 9 months ago updated by Thomas Singer 9 months ago 0

It will be comfortable to see Brunch's name in Title of Main window in Task panel

For Example:

Image 778

GUI
+1

Allow resizing any pane (including Commit pane) to any small size as long as it doesn't break UI

Hyper Sonic 11 months ago 0

As noted in https://groups.google.com/g/smartgit/c/Sy3h_ticc3w?pli=1 the commit pane cannot be resized under a certain size. Unfortunately the reply only mentioned vertical size, and I'm not sure I fully understand the reason (it could show more options, but I don't know which ones). In addition, I care about horizontal size, as I'm placing SmartGit on the left half of my monitor which leaves only 1280px width; not much to read repository names. Look below how the Commit pane is huge compared to the others:

Image 770

I don't want to change view mode or move all my panes around just for when I temporarily move SmartGit to a half monitor. I would rather have the possibility to resize things however I want, and take the responsibility to make some parts less readable than others. Plus, I don't see a reason for the minimum with on Commit pane: there is more than enough space there.