Remove environment from tooltip & fix local config issue#307
Merged
brandenrodgers merged 1 commit intomasterfrom Nov 19, 2025
Merged
Remove environment from tooltip & fix local config issue#307brandenrodgers merged 1 commit intomasterfrom
brandenrodgers merged 1 commit intomasterfrom
Conversation
camden11
approved these changes
Nov 17, 2025
brandenrodgers
added a commit
that referenced
this pull request
Dec 4, 2025
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 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.
We should only show the "environment" label in the account tooltip (shows when you hover over an account name in the "Accounts" section) if the user actually has QA accounts configured. This mostly has internal value since external customers can't have qa accounts.
This also fixes a bug for users who are using the hubspot.config.yml files instead of global config and do not want to migrate. We were always showing the migration prompt, regardless of whether the user had an existing global config or not.