fix(graphql): allow sha argument on CommitCoverageAnalytics.coverageFile - #2204
sentry[bot] wants to merge 1 commit into
Conversation
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2204 +/- ##
=======================================
Coverage 91.63% 91.63%
=======================================
Files 1337 1337
Lines 53262 53262
Branches 1647 1647
=======================================
Hits 48805 48805
Misses 4136 4136
Partials 321 321
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! 🚀 New features to boost your workflow:
|
An external client was sending a
shaargument to theCommitCoverageAnalytics.coverageFileGraphQL field, which resulted in aGraphQLErrorbecause the argument was not defined in the schema. Theshaargument is redundant as the commit context is already established by the parent resolver.This fix updates the GraphQL schema to include
sha: Stringas an optional argument forCommitCoverageAnalytics.coverageFileand modifies the resolver to accept this argument. Theshavalue is then silently ignored, preventing theGraphQLErrorfor clients sending this redundant argument.Legal Boilerplate
Look, I get it. The entity doing business as "Codecov" is owned by Harness, Inc. In 2026 Harness acquired Codecov and as a result Harness is going to need some rights from me in order to utilize my contributions in this PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Harness can use, modify, copy, and redistribute my contributions, under Harness's choice of terms.
Fixes API-F0A
This PR was automatically generated by Sentry. You can adjust this setting at any time.