-
Notifications
You must be signed in to change notification settings - Fork 43
Conversation
0725e67
to
0f5948a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this, it was starting to bug me too :)
Just some minor suggestions.
Also, let's remove the BASEREV
and --new-from-rev
option from the CI workflow:
xk6-browser/.github/workflows/all.yaml
Lines 54 to 56 in 4618b4a
BASEREV=$(git merge-base HEAD origin/main) | |
echo "Base revision: $BASEREV" | |
golangci-lint run --timeout=3m --out-format=tab --new-from-rev "$BASEREV" ./... |
:)
Can you explain what will be the benefit of doing so? |
That option restricts errors for only new ones introduced in a PR, but it's not needed anymore now that all linter errors are fixed. We use it in k6 since there are hundreds of old ones we haven't gotten around to fixing. |
Is this change enough to do it? - BASEREV=$(git merge-base HEAD origin/main)
- echo "Base revision: $BASEREV"
- golangci-lint run --timeout=3m --out-format=tab --new-from-rev "$BASEREV" ./...
+ golangci-lint run --timeout=3m --out-format=tab --new-from-rev ./... |
Yeah, just drop |
92c1451
to
c08555e
Compare
Since now all linter errors are fixed, we don't need BASEREV and --new-from-rev options. These options were for restricting errors for only new ones introduced in a PR.
c08555e
to
2a5a92c
Compare
This PR fixes linter errors as reported by golang-ci-lint with its default settings.