[chore] set entities link title #2460#2462
Merged
arminru merged 1 commit intoopen-telemetry:mainfrom Jul 4, 2025
Merged
Conversation
arminru
approved these changes
Jul 1, 2025
Contributor
|
I'd like @chalin to check this over to make sure it works in the website. |
jsuereth
reviewed
Jul 2, 2025
lmolkova
approved these changes
Jul 4, 2025
Merged
via the queue into
open-telemetry:main
with commit Jul 4, 2025
8b6bdbe
15 of 16 checks passed
spurplewang
pushed a commit
to spurplewang/semantic-conventions
that referenced
this pull request
Jul 10, 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
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.
Fixes #2460
Changes
This should result in the link title to simply be Entities rather than Entity Registry with the registry part being redundant given a user has already selected registries in the left navigation as well as it appearing as the previous breadcrumb.
Note: if the PR is touching an area that is not listed in the existing areas, or the area does not have sufficient domain experts coverage, the PR might be tagged as experts needed and move slowly until experts are identified.
Merge requirement checklist
[chore]