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

KUBESAW-250: Fixing the linter error Linter for v1.63.1 #444

Closed
wants to merge 1 commit into from

Conversation

fbm3307
Copy link
Contributor

@fbm3307 fbm3307 commented Jan 7, 2025

Would be upgrading to golangci-lint version 1.63.3 . This PR is to fix the linter error which were caught as a result of upgrading the linter

Related PR -

Copy link

sonarqubecloud bot commented Jan 7, 2025

Copy link

codecov bot commented Jan 7, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.23%. Comparing base (34f3205) to head (580eff8).
Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #444   +/-   ##
=======================================
  Coverage   78.23%   78.23%           
=======================================
  Files          49       49           
  Lines        2444     2444           
=======================================
  Hits         1912     1912           
  Misses        478      478           
  Partials       54       54           
Files with missing lines Coverage Δ
pkg/status/componentconditions.go 100.00% <100.00%> (ø)

Copy link
Contributor

@MatousJobanek MatousJobanek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, but why this cannot be part of the same PR? #442 is there any reason for creating a separate one?

@fbm3307
Copy link
Contributor Author

fbm3307 commented Jan 8, 2025

it can be, i will close this and add these changes to 442

@fbm3307
Copy link
Contributor Author

fbm3307 commented Jan 8, 2025

Closing in favour of #442

@fbm3307 fbm3307 closed this Jan 8, 2025
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.

2 participants