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

Fix GolangCI-Lint warnings #412

Merged
merged 1 commit into from
Jun 5, 2024
Merged

Fix GolangCI-Lint warnings #412

merged 1 commit into from
Jun 5, 2024

Conversation

developerkunal
Copy link
Contributor

🔧 Changes

  • Fix GolangCI-Lint warnings

📚 References

🔬 Testing

📝 Checklist

  • All new/changed/fixed functionality is covered by tests (or N/A)
  • I have added documentation for all new/changed functionality (or N/A)

@developerkunal developerkunal marked this pull request as ready for review June 5, 2024 09:09
@developerkunal developerkunal requested a review from a team as a code owner June 5, 2024 09:09
@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.37%. Comparing base (ec52c3e) to head (fdc6dee).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #412   +/-   ##
=======================================
  Coverage   95.37%   95.37%           
=======================================
  Files          47       47           
  Lines        7610     7610           
=======================================
  Hits         7258     7258           
  Misses        235      235           
  Partials      117      117           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@developerkunal developerkunal merged commit 8be5f5d into main Jun 5, 2024
7 checks passed
@developerkunal developerkunal deleted the fix-go-lint-issues branch June 5, 2024 09:59
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.

3 participants