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.

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

For Example:

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:

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.

It would be great to make it possible for repository group icons to be either with customizable colors or with customizable icon images (from a predefined set of icons for instance)

So, it would make the tree of repositories easier readable and navigable.

In the log, if a commit includes a submodule pointer commit, tag with the submodule name and use a different symbol or other graphical representation on the graph.

In the Log window, when you select 2 separate files from the same commit, the Changes pane could show the diff between them, instead of showing nothing.

This means that:
• the Changes pane won't be useless in this case, and that
• this would be like a quicker version of the Show Changes context menu item.