-
Notifications
You must be signed in to change notification settings - Fork 645
Make API key more easily available after creating a new account #19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@gankro agreed. |
The CLI should also make it discoverable. |
Right now you can type |
What needs to happen to resolve this issue? |
What happens today when you're a new user of crates.io: You visit crates.io and see this: So you click "Log in with GitHub", do the oAuth dance, and you're taken... back to the homepage, only now your icon is in the upper right: There's not really a call to action, you have to notice there's a little triangle next to your icon that opens this menu: and the menu item you want is "account settings", which is the crates.io/me page where you can verify your email and create API tokens: The smallest change is probably adding a notice at the top of the page that says something like "Welcome to crates.io! Visit account settings to verify your email address and create an API token!". Ideally, we'd only show that if we just created an account rather than updating one in the Other changes I could see that seem more complex:
I'm open to thoughts based on what people think the best experience would be and what seems possible/easy to implement! |
- Add new types for flash message - Show info type flash message after login via github - Add missed tests Small initial step to address rust-lang#19
These days, cargo tells you to go to https://crates.io/me to create an API token. If you do that without being logged in it shows a page like this: ![]() If you press the "Login" button/link it will perform the login flow and afterwards direct you to the API tokens settings page where you can create your API token. It seems to me like this covers most of the discoverability issues here. Let me know if you think that there is more that we can do :) |
Not very discoverable, especially since this is probably the first thing you're interested in getting after registering. Resetting it should definitely be in there, but that's certainly not where I would expect to go for "what is my API key".
Possible solution: redirect new logins and/or registrations to there.
The text was updated successfully, but these errors were encountered: