The situation can be recreated by initializing a new repo locally, making a commit to it, and then running git secure-fetch. You'll get stuck in a failure loop wherein you're constantly asked for your GPG PIN, a new RSL entry gets created, but it can't be pushed, so it fails, and then you start the process all over again.
Pushing the rsl ...
rsl push failed !!
fatal: ambiguous argument 'origin/rsl': unknown revision or path not in the working tree.
Something in there needs to break the circuit rather than retrying constantly.
The situation can be recreated by initializing a new repo locally, making a commit to it, and then running
git secure-fetch. You'll get stuck in a failure loop wherein you're constantly asked for your GPG PIN, a new RSL entry gets created, but it can't be pushed, so it fails, and then you start the process all over again.Something in there needs to break the circuit rather than retrying constantly.