I understand this this unlikely to ever happen, but just want to mention here that this is the direction the industry is heading, I think. Even the absolute top-end Laptops/PCs are simply nowhere powerful enough compared to what you can get using this method.

I myself am forced to stop using SmartGit after many years as well.

Also very annoyed by this change. If I say discard why would the application do stash instead? If I want to stash I say stash. Now CTRL+S and CTRL+Z do the same thing.

Assuming two remotes:

1) origin (your clone)

2) upstream (official repo)

I use 2 options:

1) For small quick work fetch upstream to local branch and work there, then right-click local branch and "push to" origin instead of upstream. Then proceed to pull-request.

2) For larger multi-people work, use origin so you can use gitflow etc. When upstream gets updated, right-click the upstream branch and merge/rebase to you origin branch to update it (just like pulling in single-origin scenario)

Nice to have but not worth "major refactoring" there are more pressing matters IMHO.

Great idea.

Personally I found myself confused with the left-side little graph so many times that I started ignoring it altogether.

Good idea, also offer to do this in popup when stash apply fails (skip conflicts).

Even better would be ability to apply stash and mark the files and conflicted just like when pulling. Although I don't know how that could be implemented.

Sorry for smart-ass reply but best solution is to merge your repos in my opinion. Only legit reason I can think of is permissions (e.g. cooperating with external teams). Otherwise I'd say KISS.

I'd say low prio as you can achieve the same with quick google search for smartgit's config folder ("smartgit config folder")

Absolutely agreed. I actually got a call once from company HQ that there is too much traffic from my station hitting the central repo. I don't remember the number but it was ridiculously high for the 2 repos I had fav'ed (I topped the "leaderboard" in a 100k+ employees corp :)

At that time I wished there was throttle option as I had to unfav one of the repos.

Not sure about this one as it would conflict with behaviour specified in official git docs:

Each line in a gitignore file specifies a pattern. When deciding whether to ignore a path, Git normally checks gitignore patterns from multiple sources, with the following order of precedence, from highest to lowest (within one level of precedence, the last matching pattern decides the outcome):

• Patterns read from the command line for those commands that support them.
• Patterns read from a .gitignore file in the same directory as the path, or in any parent directory, with patterns in the higher level files (up to the toplevel of the work tree) being overridden by those in lower level files down to the directory containing the file. These patterns match relative to the location of the .gitignore file. A project normally includes such .gitignore files in its repository, containing patterns for files generated as part of the project build.