This is the year that GitHub will require anyone who contributes code to enable 2FA, and we continue to see them improve how we use 2FA this week. As I previously mentioned, the changes we see out of GitHub this year will be an excellent opportunity for us to learn how to do 2FA better.
You can now disassociate your email address from your locked GitHub account. As GitHub mentions when enabling 2FA, if you lose access to your second factor and recovery codes, there is no way to regain access to your account. With this latest enhancement, if you find yourself in that situation, you can disconnect your email from that account to create a new account.
While creating a new account would change the read-only email account that GitHub generates for you, if you use your actual email address, all your commits would transfer over to that new account.
GitHub also made it easier to set your preferred 2FA method. This will hopefully make it easier for you should you need to log in from another device or use sudo mode. I didn’t see the point of this change at first. Then I remembered a brief time when GitHub decided I should always use the mobile app to verify myself even though I had my security key already connected to my computer.
Moving away from 2FA, if you use JetBrains Gateway and are a .NET developer, you’ll be excited to hear that CodeSpaces now has a beta for Rider. I would love to hear how this goes for anyone using it.
Also, code search and code view are now in a public beta. I had some initial issues with code search, but over the past few weeks, I’ve not run into any, so hopefully, they have gotten all the kinks worked out as they enter into the public beta.
Were there any GitHub announcements I missed that caught your eye?
Dan Cook 