3 ms·
Two things: 1. 2FA does not require your phone number. 2. If you don't already, you should use a public key for pushing your commits It's highly unlikely tha
by codemusings 3y ago
Two things:
1. 2FA does not require your phone number.
2. If you don't already, you should use a public key for pushing your commits
It's highly unlikely that you lose commit access even if you don't complete the "enrollment" unless you use http authentication for pushing commits in which case you should realize that password security is a huge liability for any big web application and I recommend you reconsider your approach.
- follower 3y ago> highly unlikely that you lose commit access even if you don't complete the "enrollment" This statement does not appear to be correct. According to the roadmap graphic[0] (that has no useful accessibility alt text) it says 7 days after deadline "Blocked from accessing GitHub features until you enable 2FA". [0] https://github.blog/2022-12-14-raising-the-bar-for-software-security-next-steps-for-github-com-2fa/ https://github.blog/2022-12-14-raising-the-bar-for-software-...
- codemusings 3y agoSure, but are basic git operations the same as Github features (PRs, Code Review, Actions, etc.)? In any case. Leaving Github in defiance of 2FA requirements seems ill-conceived.