-
Notifications
You must be signed in to change notification settings - Fork 515
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
sparkles: add ListProgrammingLanguages
for Azure DevOps
#4432
sparkles: add ListProgrammingLanguages
for Azure DevOps
#4432
Conversation
The Fuzzing check now completes
|
Signed-off-by: Jamie Magee <[email protected]>
889bebc
to
1a6d159
Compare
Looks like the test zip file and an actual zip file from Azure DevOps are different. Here's the test data Details
And the scorecard repository Details
|
Signed-off-by: Jamie Magee <[email protected]>
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #4432 +/- ##
==========================================
+ Coverage 66.80% 68.53% +1.73%
==========================================
Files 230 240 +10
Lines 16602 17879 +1277
==========================================
+ Hits 11091 12254 +1163
- Misses 4808 4823 +15
- Partials 703 802 +99 |
Getting closer to a complete run Details
Still missing:
|
Signed-off-by: Jamie Magee <[email protected]>
9704cac
to
75b3bf2
Compare
Signed-off-by: Jamie Magee <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
What kind of change does this PR introduce?
What is the current behavior?
ListProgrammingLanguages
throws an unsupported error for Azure DevOpsWhat is the new behavior (if this is a feature change)?**
Which issue(s) this PR fixes
Next step of #4177
Special notes for your reviewer
I also fixed a bug in the zip implementation when testing the
Fuzzing
checkDoes this PR introduce a user-facing change?
For user-facing changes, please add a concise, human-readable release note to
the
release-note
(In particular, describe what changes users might need to make in their
application as a result of this pull request.)