Better explanation on OTP #24
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Use the defaut OTP explanation everywhere except when the context is "OTP-aware" (like when setting double-authentication)
jdeniau force-pushed the otp-explanation-on-more-endpoints branch from 1a00846 to 7a3629b Compare 
zkat approved these changes Jul 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Re-import of npm/npm#21119
Use the defaut OTP explanation everywhere except when the context is "OTP-aware" (like when setting double-authentication).
@zkat I followed your recommendation about
npm login, I just changed the message a little to be more understandable than the previous one, but not as verbose as the default one ;)