Skip to content

Conversation

@cbandy
Copy link
Member

@cbandy cbandy commented Jul 10, 2025

We used golangci-lint migrate to get to v2, and that dropped the configuration comments we had in v1. This puts those back, enables new linters available in v2, and updates the "next" configuration similarly.

Checklist:

  • Have you added an explanation of what your changes do and why you'd like them to be included?
  • Have you updated or added documentation for the change, as applicable?
  • Have you tested your changes on all related environments with successful results, as applicable?
    • Have you added automated tests?

Type of Changes:

  • Testing enhancement

@cbandy

This comment was marked as resolved.

@cbandy cbandy force-pushed the more-linters branch 2 times, most recently from 9c77f66 to c7e2d19 Compare July 10, 2025 17:47
awk >> "${GITHUB_STEP_SUMMARY}" '
NR == 1 { print "```json" } { print } END { if (NR > 0) print "```" }
' || true
golangci-lint run --config .golangci.next.yaml --show-stats >> "${GITHUB_STEP_SUMMARY}" \
Copy link
Member Author

Choose a reason for hiding this comment

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

@cbandy
Copy link
Member Author

cbandy commented Jul 10, 2025

A variety of KUTTL tests were failing, so I reverted my changes in pgbackrest.go and disabled the predeclared linter.

@cbandy cbandy merged commit 82909e9 into CrunchyData:main Jul 11, 2025
30 of 31 checks passed
@cbandy cbandy deleted the more-linters branch July 11, 2025 15:48
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