Make CI job shields in README point to v3 branch and releases#1735
Merged
Conversation
# Details - Stop showing red "CI failing" labels in README just because CI jobs of some random ongoing PR fail. - Make those labels/shields point to v3 branch instead. - Make the `mediasoup-worker-prebuild` CI shield point to "releases" since it doesn't run on v3 branch bu design. - Also add some paths to `mediasoup-worker-clang-tidy.yaml`. - Also make `mediasoup-worker-clang-tidy.yaml` CI job run on push on v3 branch so we display its status in v3 in the shield rather than the status of the latest ongoing PR.
jmillan
approved these changes
Feb 18, 2026
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.
Details
mediasoup-worker-prebuildCI shield point to "releases" since it doesn't run on v3 branch bu design.mediasoup-worker-clang-tidy.yaml.mediasoup-worker-clang-tidy.yamlCI job run on push on v3 branch so we display its status in v3 in the shield rather than the status of the latest ongoing PR.