-
Notifications
You must be signed in to change notification settings - Fork 354
[infra] Fix OneCollector Dangerous-Workflow #3227
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[infra] Fix OneCollector Dangerous-Workflow #3227
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #3227 +/- ##
==========================================
+ Coverage 69.93% 69.95% +0.02%
==========================================
Files 440 440
Lines 16974 16974
==========================================
+ Hits 11870 11874 +4
+ Misses 5104 5100 -4 Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
24ed859 to
ed81acd
Compare
|
Tested also on my fork, check outing looks good. Dummy changes removed |
|
Unfortunately, it didn't fix the issue. I have missunderstand the go-lang scanning code. |
Fixes Scorecard -->
Dangerous-Workflow https://scorecard.dev/viewer/?uri=github.com/open-telemetry/opentelemetry-dotnet-contrib
Changes
In general, it is doing the same as previously, but it makes scorecard happy.
Merge requirement checklist
[ ] Unit tests added/updated[ ] AppropriateCHANGELOG.mdfiles updated for non-trivial changes[ ] Changes in public API reviewed (if applicable)