credential.helper=cache only works before starting lazygit

[rayluo]

Describe the bug
Background: In some of my environments I'm using a normal password (i.e. not ssh key), and I use git credential.helper cache to reduce the need to input password everytime. It works by git spawning a background cache-daemon.

Such mechanism still works, if I perform one such login in normal git command line, and then start to do all the pull/push inside lazygit.
But it will not work if I use lazygit without that cache-daemon being pre-existing. It is possibly because git's cache daemon attaches itself to current process's parent, but perhaps lazygit uses an intermedium and temporary "bash" process so that the daemon got killed?

[jesseduffield]

That's right: lazygit either runs git directly (no bash involved) or via a short-lived bash process. Not sure how to get around this one.

[rayluo]

Fair enough. Until we would have a real solution, I would suggest @jesseduffield you convert this github issue into a github discussion, and mark it as "answered", so that it would at least become a known workaround for more audience.

[slieschke]

I ran into what looks like the same problem using cache with an OAuth credential helper. With lazygit open I got a browser authorization every minute, once per auto-fetch, because the cache daemon started by lazygit's fetch didn't survive it.

Git has an option that fixed it for me, credentialCache.ignoreSIGHUP:

git config --global credentialCache.ignoreSIGHUP true

followed by restarting the daemon (git credential-cache exit) so it picks up the setting.

It was originally added for a similar situation with Emacs, where the daemon gets a SIGHUP when the git command that started it exits. I haven't tested it with plain passwords, but the option only affects the daemon, not what it's caching, so it should behave the same.