Thank you, that will be perfect!

I would like a setting to make it never choose "Ignore as a pattern" automatically.  The user can select the option on the dialog if necessary.

My problem is that when the pattern matches common source file types (e.g. "*.h" or "*.java") then new files that are not generated by external tools (e.g. SWIG) are also ignored because the pattern "*.h" or ".java" is in the ignore file.

This is not limited to single file selection though it always does it when a single file is selected.

We exclusively use ".gitignore in repository root directory" and would love to be able to choose this as the default option. I would be fine if this is a low-level option that I can tell users in our company to use.

Regarding why we use it: having .gitignore files littered throughout a repo makes it very difficult to find where/why a particular file is ignored/missing etc. Having a single file also makes managing .gitignores in our >100 repositories much easier for scripts, etc.

I do not suppose there has been any further examination of this request? Not realising you have not pushed a local gitflow branch has bitten a number of our developers. We work with over a hundred repos in a particular project so pushing all repos every time over a slow 10Mbit internet connection while working from home is not always feasible.

I have also been caught out by this on a number of occasions. I understand that there are use cases where a user might want to only work locally, but when working with gitflow it often happens that feature/release/hotfix branches are created, often across a number of repos, and then a user forgets to push one or more of these repos since the icons indicate that everything is already pushed/up to date.

Hi, this is not quite a duplicate. I am already using the groups-within-groups, but would like some more operations on them - recursive opening and the ability to see changes in the whole hierarchy. I tried to detail these in the list after the code block above. Let me know if I am not clear about something. I am currently using SmartGit 9.1.1.

The cancel option in the Output window while doing a background fetch in SmartGit 19.1.1 meets my needs, thanks. The current git operation completes and then returns control to the user. 

I am also running into this situation. Our projects consist of many repo's (> 50) and when background fetching is happening there is no way to interact with any of the repositories. Two possible solutions:

• Only disable the UI for the repo currently being fetched in the background so that we can interact with the other repos. It is fine if it still disables interacting with multiple repos together, e.g. in a group.
• Add a button to cancel the background fetches (possibly letting the current git operation complete, but not starting the next one as Jeff suggests).

Thanks for the implementation in SmartGit 18.1 The combo-box drop-down menu on the Ignore dialogue is precisely what I was looking for.

It would be handy to be able to do this even if only one repo could be selected at a time. When I said "Flat" view, what I mean is that when a (single) repo is selected, Smartgit can be configured to show all files in a flat structure, independent of sub-directories (within the repo). This is my normal way of working with a single repo. It agree it would be challenging to try implement this when multiple repos are selected/open/viewed at the same time, but I would be happy with the ignore option defaulting to current (or light-weight) behaviour for the multiple repo case.