-
Notifications
You must be signed in to change notification settings - Fork 563
fix: don't run the linter on non code changes #817
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
Conversation
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.
LGTM although I'd like the option to run linters on doc changes in future.
- name: Set up Go | ||
uses: actions/setup-go@v2 | ||
with: | ||
go-version: "1.16" |
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.
1.16
is the required version now for Starport. Should we rollback this change?
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.
The linter should be a prebuilt binary. You don't need to install go I believe
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.
Tested with #819, seems like removing version is not a problem indeed. While we were using the alpha version of 1.16
, it was somewhat required to manage Go installation ourselves because linter was not able to use non stable releases. I think the reason is the linter somehow uses go
cmd under the hood or depends on a Go installation in some other way.
No description provided.