Skip to content

Fix golangci-lint warnings #2264

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

Merged
merged 2 commits into from
May 22, 2025
Merged

Fix golangci-lint warnings #2264

merged 2 commits into from
May 22, 2025

Conversation

chipshort
Copy link
Collaborator

No description provided.

Copy link

codecov bot commented May 19, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 45.19%. Comparing base (adea2f9) to head (f81fbf0).
Report is 39 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #2264      +/-   ##
==========================================
+ Coverage   45.18%   45.19%   +0.01%     
==========================================
  Files          79       79              
  Lines       10934    10933       -1     
==========================================
+ Hits         4940     4941       +1     
+ Misses       5556     5555       -1     
+ Partials      438      437       -1     
Files with missing lines Coverage Δ
app/upgrades.go 84.48% <ø> (-0.27%) ⬇️

... and 1 file with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@chipshort chipshort marked this pull request as ready for review May 20, 2025 10:43
Copy link
Contributor

@pinosu pinosu left a comment

Choose a reason for hiding this comment

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

LGTM 👍

@chipshort chipshort merged commit 3246f6a into main May 22, 2025
19 checks passed
@chipshort chipshort deleted the co/fix-linter-warnings branch May 22, 2025 11:35
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