Add feature to seach by content in Files-panel.
Now it's only possible in Graph-panel.

Currently, you can only search within lines, but I sometimes search for multiple ones (a code block) in order to ensure whether it's duplicated in the same file or not.

Hi,

just a feedback, but IMO the naming scheme for the "updates" could be improved. I provide details as follows.

Under tab menu Help, one finds two options

• Check for New Version
• Check for Latest Build

At the same time, users receive notifications "XXX RC available".

Findings

Firstly, checking a "New Version" sounds like checking for an "overall" new version, which is translates like "Latest Build", but what it actually means is an increment of the currently installed version, right? Exactly that should be made clear. "New Version" means "Version increment of currently installed release".

Secondly, the "RC" translates to what exactly, the same as "Latest Build"? Then that should be made clear (harmonized) in the notifications or at the same time in the Help menu: "Check for Latest Build or Release Candidate". (Suppose both have the same meaning)

Thirdly, what is the numbers game behind all this: The "New Versions" are what, this: 22.1.7 #19285, or that 22.1.7 #19285? Then follows, what is the RC, a major increment, such as 23.0.0?

As a suggestion make it clear, what is going on to someone not using this every day and not so much caring about atomic updates. Which name implies which and what increments should worked out. Also, which updates float or de-evaluate the current license (if this is necessary in this context)? Does the license continue to work with RC "upgrade"? Provide the information first.

Kind regards

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

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

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.

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).

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!

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

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:

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)

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.