Yep - this has been stressing me out since I first heard about the change on GitHub's end. I'm probably going to just have to stop using SmartGit for one set of repos until multi-account support comes in some form. :(

(weird that I only just got the email notification about your comment now!)

Oops sorry I never replied to this, a whole bunch of stuff came up and it slipped my mind.

As an update, the problem I'm having (not sure if this was happening back then or not, but it is now) is that when I input my username/password, it says that the credentials are incorrect (perhaps because I have 2FA set up on my GitHub account? I don't get this error on my other GitHub account that doesn't have 2FA). Setting up a personal access token doesn't help.

In my mind, a nice workaround feature would be:

If there are multiple github.com hosting providers set up with OAuth, the first time a repo needs access the user gets presented with a popup window where they have to select which OAuth token to use. If the operation is successful, that selection is then cached in association with the repo in question. If not, they get the popup again, and if the popup is closed, then it just proceeds with the operation without any authentication. This could also be an option in the Repository -> Settings panel perhaps?

Yeah I tried that but it kept asking for username/password every time I pushed, which ended up being more of a hassle than just changing hosting accounts.

Just to throw my hat in the ring: it's totally up to you, but having just switched to smartgit from gitkraken (since the latter is full of bugs), this is (so far) the only feature that I'm seriously missing.

Having to go through each file and read its path to ensure that it's in the directory I'm meant to be working in before staging/commiting adds heaps of cognitive load to setting up commits. Working in Unity means that often lots of random files are updated in other directories while the application is running and generally I don't want to stage those (to keep commits clean). I imagine many other people have similar workflows of using directories to check that they're not committing things they shouldn't be / to group commits.

If I could offer a suggestion for the problem of duplicate selections - selecting/deselecting a folder should just apply its selection state to all files and folders inside of it. Having it as a non-default option would mean that, even if it's 'suboptimal', the users who prefer it could still have it enabled.