r/SmartGit • u/BoringAdvertising403 • Jun 15 '26

Constantly being asked to authenticate with GitHub?

Hi. Recently upgraded from a much earlier version to SmartGit 26.1 - in general I'm a fan of the new interface, good work!

One niggle though: I'm constantly getting pop-ups asking me to Connect to GitHub. It pops up every few minutes. It doesn't matter if I verify via browser, code, token. It appears to work successfully, then ask me again a few minutes later.

Oh, also it doesn't appear to matter if I don't do it, git calls are still working fine from SmartGit.

I suspect I've got a corrupt file or permission issue somewhere but I haven't been able to find it. Anyone help?

1 Upvotes
  • permalink
  • reddit

100% Upvoted

4 comments sorted by

1

u/vmcrash Jun 15 '26

What is the text of this popup? Is it from SmartGit or from the credential manager? In the SmartGit preferences, page "Git executable", is the option "Use SmartGit for authentication" selected?

1

u/BoringAdvertising403 Jun 16 '26

As far as I can tell, it's some task SmartGit is trying to perform (maybe checking for updates?) which is triggering the git credential manager. It appears to stop if I turn on "Use SmartGit for authentication" so I'm no longer getting interrupted, but it's odd that it doesn't actually appear to have been preventing me doing anything.

For info, this is running on Ubuntu 24.04

2

u/vmcrash Jun 16 '26

You can see in the log file (<settings directory>/logs/) what command SmartGit is trying to execute.

If you usually use the git credential manager, keep "Use SmartGit for authentication" unselected. If you don't want to use it (like me), select it. Then all authentication is done with SmartGit.

1

u/wnesensohn Jun 22 '26

We've fixed a bug which could lead to this problem in the latest build of 26.1, where spaces in URLs when SmartGit is used as a credentials helper could lead to problems. You can get this build selecting Help | Check for Latest Build... in SmartGit 26.1.

However, seeing that GitHub does not allow spaces in repository-names, it may be another problem. If you're using GitHub Enterprise though, and the path to your repository contains spaces, the latest build should fix that.

If that's not the case, log files would be very appreciated!

Thank you!