You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm a big believer in treating warnings as errors. Sure, many warnings are false positives, but if a normal build has warnings, you're likely to overlook any new ones that indicate a real problem.
For the sake of the -Werr aficionados out there, add a lint_strictly setting¹ that sends the --strict flag to helm lint.
¹ Just calling it strict might be ok, but the struct field in internal/helm.Config should definitely have "Lint" in the name somewhere since the setting is specific to that command.
The text was updated successfully, but these errors were encountered:
I'm a big believer in treating warnings as errors. Sure, many warnings are false positives, but if a normal build has warnings, you're likely to overlook any new ones that indicate a real problem.
For the sake of the
-Werr
aficionados out there, add alint_strictly
setting¹ that sends the--strict
flag tohelm lint
.¹ Just calling it
strict
might be ok, but the struct field ininternal/helm.Config
should definitely have "Lint" in the name somewhere since the setting is specific to that command.The text was updated successfully, but these errors were encountered: