Pipedv1 reports plugins while report metadata#5552
Merged
khanhtc1202 merged 2 commits intomasterfrom Feb 7, 2025
Merged
Conversation
Signed-off-by: khanhtc1202 <khanhtc1202@gmail.com>
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #5552 +/- ##
==========================================
- Coverage 26.44% 26.44% -0.01%
==========================================
Files 465 465
Lines 49862 49872 +10
==========================================
Hits 13188 13188
- Misses 35620 35630 +10
Partials 1054 1054 ☔ View full report in Codecov by Sentry. |
t-kikuc
approved these changes
Feb 7, 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.
What this PR does:
as title
Why we need it:
Piped need to report plugins as it metadata, so we can use this info on Web UI application form
Which issue(s) this PR fixes:
Part of #5252
Follow #5545
Does this PR introduce a user-facing change?: