Skip to content

Update README.md after repository rename#20

Open
hdamker wants to merge 1 commit intomainfrom
fix/update-readme-after-rename
Open

Update README.md after repository rename#20
hdamker wants to merge 1 commit intomainfrom
fix/update-readme-after-rename

Conversation

@hdamker
Copy link
Contributor

@hdamker hdamker commented Feb 20, 2026

What type of PR is this?

  • cleanup

What this PR does / why we need it:

Updates all references from DeviceQualityIndicator to DeviceMediaStreamingRate in README.md after the repository rename. This includes badge URLs, heading, and description text.

Which issue(s) this PR fixes:

Fixes #13
Related to camaraproject/APIBacklog#296

Special notes for reviewers:

Straightforward find-and-replace of the old repository name. No content changes beyond the name.

Changelog input

 release-note
n/a

Additional documentation

This section can be blank.

docs

@github-actions
Copy link

🦙 MegaLinter status: ✅ SUCCESS

Descriptor Linter Files Fixed Errors Elapsed time
✅ ACTION actionlint 2 0 0.01s
✅ API spectral 1 0 1.4s
✅ REPOSITORY git_diff yes no 0.01s
✅ REPOSITORY secretlint yes no 0.56s
✅ YAML yamllint 1 0 0.33s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by OX Security

* Service API “DeviceMediaStreamingRate” (see [APIBacklog.md](https://github.com/camaraproject/APIBacklog/blob/main/documentation/APIbacklog.md))
* The API provides the customer with the ability to:
* Get insights about the network status of a defined mobile device.
* For this the API will return an indicator which is bundeling information about the device network status such as availibilty, open datavolume, congjestion, historical congjestion or the connecitvity status (2G, 3G, 4G, 5G).
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@maheshc01 please adapt the scope to the actual scope of the media-streaming-rate API

@hdamker
Copy link
Contributor Author

hdamker commented Feb 20, 2026

@maheshc01 please review and suggest an updated scope, so that we can merge this PR soon. The repository is already renamed (but the links will still work for now).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

update the name for the API repo

1 participant