Skip to content
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

[chore]: enable expected-actual rule from testifylint #6154

Merged
merged 2 commits into from
Sep 25, 2024

Conversation

mmorel-35
Copy link
Contributor

Description

Testifylint is a linter that provides best practices with the use of testify.

This PR enables expected-actual rule from testifylint

@mmorel-35 mmorel-35 force-pushed the testifylint/expected-actual branch from a7cfcc4 to 4833d1d Compare September 24, 2024 20:16
@mmorel-35 mmorel-35 requested a review from pellared September 24, 2024 20:17
Copy link

codecov bot commented Sep 24, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 66.8%. Comparing base (f188a52) to head (c83d13f).
Report is 1 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##            main   #6154     +/-   ##
=======================================
- Coverage   66.8%   66.8%   -0.1%     
=======================================
  Files        206     206             
  Lines      13207   13207             
=======================================
- Hits        8829    8827      -2     
- Misses      4111    4112      +1     
- Partials     267     268      +1     

see 1 file with indirect coverage changes

@pellared pellared merged commit 9207da4 into open-telemetry:main Sep 25, 2024
25 checks passed
@mmorel-35 mmorel-35 deleted the testifylint/expected-actual branch September 25, 2024 17:56
@MrAlias MrAlias added this to the v1.31.0 milestone Oct 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants