GitHub will start requiring developers to enable two-factor authentication from March 13, 2023

From March 13, 2023, GitHub will begin notifying "development teams and administrators" of the need to add two-factor authentication (2FA). First, small and then large communities will receive an email or see the corresponding banner on the site.

After the first notification, users will receive 45 days to set up and during this time they will receive regular reminders. If the developer does not want to wait for his turn, he can connect 2FA right now — using the instructions.

There are several ways of additional authentication — SMS, security keys, login via the GitHub Mobile application and TOTP (generation of one-time codes). But the company warns that SMS is not considered the most reliable option, and advises to connect TOTP with it.
Within 28 days after connecting, GitHub will ask you to check the work of 2FA, and in case of an error, it will offer to reset the settings without disabling access to the account.

Developers who do not make it on time will receive an additional week to set up starting from the first login after 45 days have expired. Reminders will be sent throughout all seven days. If the user still does not connect 2FA, he will be restricted access to the account.
GitHub announced plans to ensure the transition of all users to 2FA by the end of 2023 in May 2022.