On March 13, we will officially begin rolling out our initiative to require all developers who contribute code on GitHub.com to enable one or more forms of two-factor authentication (2FA) by the end of 2023. Read on to learn about what the process entails and how you can help secure the software supply chain with 2FA.
I don’t. Not sure whether they even provided those when I have set it up, maybe they thought that since it’s stored online you can’t just lose it, but I really don’t remember whether there was any I could have saved. It way years ago.
Also, thinking about it, the prompt does not give an option to use a recovery code, but only to try with the phone number (which is dead by now), or contact support.
tbf, that’s a bit on you. The whole point of 2FA is to prove that you are you. and if you completely killed that factor without deactivating it first or having a backup in any way, I can see the support not doing much. I’d be pissed if someone could just contact support and deactivate my 2FA method
do you have the backup codes somewhere? Could help
I don’t. Not sure whether they even provided those when I have set it up, maybe they thought that since it’s stored online you can’t just lose it, but I really don’t remember whether there was any I could have saved. It way years ago.
Also, thinking about it, the prompt does not give an option to use a recovery code, but only to try with the phone number (which is dead by now), or contact support.
tbf, that’s a bit on you. The whole point of 2FA is to prove that you are you. and if you completely killed that factor without deactivating it first or having a backup in any way, I can see the support not doing much. I’d be pissed if someone could just contact support and deactivate my 2FA method