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 G202 rule for gosec #12984

Merged
merged 1 commit into from
Apr 3, 2023
Merged

chore: Enable G202 rule for gosec #12984

merged 1 commit into from
Apr 3, 2023

Conversation

zak-pawel
Copy link
Collaborator

resolves #12903

@Hipska Hipska added the ready for final review This pull request has been reviewed and/or tested by multiple users and is ready for a final review. label Mar 30, 2023
Copy link
Member

@srebhan srebhan left a comment

Choose a reason for hiding this comment

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

LGTM. Thanks for fixing the issues @zak-pawel!

@srebhan srebhan merged commit 0de59d4 into influxdata:master Apr 3, 2023
srebhan pushed a commit that referenced this pull request Apr 3, 2023
Co-authored-by: Pawel Zak <Pawel Zak>
(cherry picked from commit 0de59d4)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore linter ready for final review This pull request has been reviewed and/or tested by multiple users and is ready for a final review.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Linter: gosec, Rule: G202 - SQL query construction using string concatenation. Should we enable it?
4 participants