[iso1631]

Agree, it's painful, and it really takes me out of the larger point they are trying to make

A workflow should be be

    User creates an SSH key pair, the private key never leaving the computer
    User sends public key to authoriser
    Authoriser pushes public key to Git (presumably an email + key touple?)
    Wait for the build job to finish (not sure what this does)
    Build process sends the email saying "You can now use your key"

Same with say a wireguard key. Or an SSL certificate.

I think the larger point is that you just have step by step instructions, and thus dont need to catch edge cases, but it also makes it harder to avoid skipping a step, which seems reasonable (I do this myself in some areas)