When trying to push my changes to my remote repo, node-red is not initiating the push. Just the following progress display is appearing for some milliseconds.
What I miss is that node-red is asking for the private key for my id_rsa. Days ago, when I set up the remote connection, this was working fine. But now it stoped working. Also a restart of the node-red service is not helping.
If it did initially work and now does not due to the private key not being unlocked then it must have been unlocked when you first tried. Either you need an unlocked key or you need a key manager that lets you unlock it.
I don't use git with node-red so I don't have an exact answer. However, with recent npm attacks, I do now use signed git commits which require an unlocked key and I use a secrets manager for that. I'm currently using Kleopatra for that.
The point of an external key manager is to manage the keys in a dedicated, security-focused tool away from other systems and services that might get compromised. Or, as in Node-RED's case, where anyone who can amend a flow would be able to get your pass code.
The 2nd point is to be able to automate service restarts without human intervention. The key manager takes care of it so if Node-RED has to restart for some reason, you don't have to have a person with access to the server to manually put in the passcode before it will restart.
