Can't push due to message: Are you sure you want to continue connecting?

[raphaklaus]

Topic
When connecting with GitHub for the first time, the host is unknown and ask if we should proceed connecting. The UI seems to not understand that as a expected input from the user.

Your thoughts
As in other situations, there is a pop-up to insert an input to proceed. I think in this situation it should behave the same. Are we able to capture this message and treat accordingly?

[mark2185]

Just to clarify, is this when you're using ssh?

How often does this happen, once per device?

[raphaklaus]

That happens the first time connecting with SSH. I manage to run the git command outside of the lazygit and it, per definition, never happened. I think for consistency sake Lazygit should know to treat these cases but I understand that might be difficult.

[zocker-160]

I just had the same when adding a new remote, it gets stuck forever:

[lunacd]

How often does this happen, once per device?

This doesn't happen very often. It's once per device per user per host public key. Say I'm on the same device, same user, but now I'm pushing to SourceHut instead of GitHub, it happens again. Say I'm still pushing to GitHub, but GitHub rotated their public key, it happens again.

I wouldn't say this has a high priority, but this is likely to occur in an user's first encounter with lazygit. From a perspective of retaining potential users, I'll say yes let's add an popup to handle this scenario.

[hangj]

Same here, too

[redbeardymcgee]

I ran into this after changing my remote to an SSH URI. Out of initial laziness, I cloned down my nix flake repo over HTTPS to get my system up and running. After achieving enough configuration to run the new desktop, I was ready to push my commit up so I set my remote URL. The log was then stuck waiting for verification of the key authenticity. I had to jump into a separate terminal and trigger the verification again, then lazygit was able to work after launching it again.