Try to explain how to deal with secure 2fa requirements#40665
Try to explain how to deal with secure 2fa requirements#40665jsoref wants to merge 2 commits intogithub:mainfrom
Conversation
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. The table shows the files in the
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server 🤖 This comment is automatically generated. |
|
@jsoref Okay, this looks like a suitably modest change to me. I will try to figure out whom I need to speak to for approval, and hopefully having actual wording will make that process easier. 🤞 |
|
A stale label has been added to this pull request because it has been open 30 days with no activity. If you think this pull request should remain open, please add a new comment. |
|
@Sharra-writes any luck in finding the designated reviewer? Surely this shouldn't be taking two months |
Enabling Secure 2FA requirements results in lots of confusing outcomes for people and there really isn't good text anywhere to help people. This is one step to try to improve the story a bit.
Why:
Only allow secure two-factor methods#38087 (comment)What's being changed (if available, include any code snippets, screenshots, or gifs):
Check off the following: