Conversation
Align the API name with the repository name (#38): - API definition file renamed to device-media-streaming-rate.yaml - info.title, tags, servers.url, security scope, schema names and description references updated accordingly - Test definitions renamed to device-media-streaming-rate.feature with matching resource path and scenario tags release-plan.yaml is updated separately in #48, as the validation rules require release-plan changes to be in their own PR.
maheshc01
force-pushed
the
rename/device-media-streaming-rate
branch
from
September 14, 2026 18:00
53edfb3 to
03995c0
Compare
This was referenced Sep 14, 2026
Contributor
Author
|
Closing for now to keep things simple. The rename will be re-submitted as a fresh PR against main once #47 is merged; the branch rename/device-media-streaming-rate stays in place. |
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
1 participant
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.
What type of PR is this?
What this PR does / why we need it:
Aligns the API name with the repository name, as requested in #38:
device-media-streaming-rate.yamlinfo.title→ Device Media Streaming Rate; tags,servers.url({apiRoot}/device-media-streaming-rate/vwip), security scope, schema names and description references updated accordinglydevice-media-streaming-rate.featurewith matching resource path and scenario tagsThis is a pure name substitution on top of #47; no other content changes.
Which issue(s) this PR fixes:
Fixes #38
Special notes for reviewers:
rc-prep/review-findings). Merge Address r1.1 review findings in the API definition and test definitions #47 first; this PR then retargets tomain.media-streaming-rate.yamlnot found) and P-019 (orphandevice-media-streaming-rate.yaml) untilrelease-plan.yamlnames the new API. That update is in Release plan: r1.2 release candidate on Commonalities r4.4 #48 and, by rule P-022, cannot be part of this PR. Neither PR can be green while the other is unmerged; the spec and feature file themselves have no findings. Intended order: Address r1.1 review findings in the API definition and test definitions #47, then this PR, then Release plan: r1.2 release candidate on Commonalities r4.4 #48.Changelog input
Additional documentation