8000 fix: don't run the linter on non code changes by alessio · Pull Request #817 · ignite/cli · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

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

Merged
merged 1 commit into from
Mar 7, 2021

Conversation

alessio
Copy link
Contributor
@alessio alessio commented Mar 4, 2021

No description provided.

@alessio alessio requested review from fadeev, ilgooz and lumtis as code owners March 4, 2021 22:26
@alessio alessio changed the title don't run the linter on non code changes fix: don't run the linter on non code changes Mar 4, 2021
@alessio alessio requested a review from barriebyron March 5, 2021 00:01
Copy link
Contributor
@barriebyron barriebyron left a 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"
Copy link
Member

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?

Copy link
Contributor Author

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

Copy link
Member

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.

@ilgooz ilgooz merged commit 5268361 into develop Mar 7, 2021
@ilgooz ilgooz deleted the alessio/avoid-running-lint-on-non-code-changes branch March 7, 2021 17:15
@alain2sf alain2sf restored the alessio/avoid-running-lint-on-non-code-changes branch March 9, 2021 21:28
@Pantani Pantani deleted the alessio/avoid-running-lint-on-non-code-changes branch February 24, 2022 21:57
Jchicode pushed a commit to Jchicode/cli that referenced this pull request Aug 9, 2023
768A
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.

3 participants
0