feat: Unify naming to 'User Auth Tokens'#50154
Merged
Merged
Conversation
github-actions
Bot
added
the
Scope: Frontend
scttcper
approved these changes
Jun 1, 2023
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This unifies the naming to "User Auth Tokens" everywhere. Previously, we were using
API keysin the user dropdown, andAuth Tokensin the account settings page. Renaming this makes this more explicit and also prepares us for having more types of access tokens (e.g. org based) in the future.As far as I can tell (based on a search) we only reference this by URL in the docs (e.g. see: https://docs.sentry.io/platforms/javascript/sourcemaps/uploading/webpack/), so should be fine from that perspective.