Skip to content
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

fix: make linting work on 45 #13185

Merged
merged 10 commits into from
Sep 8, 2022

Conversation

faddat
Copy link
Contributor

@faddat faddat commented Sep 7, 2022

Description

in the 45 series sdk, we didn't check out the repository before running the linter, so it always passes


Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

  • included the correct type prefix in the PR title
  • added ! to the type prefix if API or client breaking change
  • targeted the correct branch (see PR Targeting)
  • provided a link to the relevant issue or specification
  • followed the guidelines for building modules
  • included the necessary unit and integration tests
  • added a changelog entry to CHANGELOG.md
  • included comments for documenting Go code
  • updated the relevant documentation or specification
  • reviewed "Files changed" and left comments if necessary
  • confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

  • confirmed the correct type prefix in the PR title
  • confirmed ! in the type prefix if API or client breaking change
  • confirmed all author checklist items have been addressed
  • reviewed state machine logic
  • reviewed API design and naming
  • reviewed documentation is accurate
  • reviewed tests and test coverage
  • manually tested (if applicable)

@faddat
Copy link
Contributor Author

faddat commented Sep 7, 2022

so, now it is actually trying to run the linter

@faddat
Copy link
Contributor Author

faddat commented Sep 7, 2022

basically, if we don't mind, then no problem.

But 45's probably never had a run of the linter in ci.

@faddat
Copy link
Contributor Author

faddat commented Sep 7, 2022

ok, so, I'll walk through the PR-- and BTW, if we don't care about this, it is OK.

But to make a long story short, linting in 45 passed previously, not becuase of a defined version of the linter, but instead because we did not check the repo out in lint.yml

so it would always be "no changes here" and we would get a green tick, wheather or not linting passed, because linting didn't run.

NB: after some number of issues, the linter stops listing them. The CI likely shows an incomplete list of issues.

https://github.com/cosmos/cosmos-sdk/runs/8237391169?check_suite_focus=true

@tac0turtle
Copy link
Member

okay lets fix it. sorry about the nitting

@faddat
Copy link
Contributor Author

faddat commented Sep 8, 2022

Oh no it's not a problem at all

The fact is unfortunately you're correct, I have the same concern about this

What I'll do is I'll write this today and then let's kind of see what happens next

@faddat faddat changed the title chore: make linting work on 45 fix: make linting work on 45 Sep 8, 2022
@faddat
Copy link
Contributor Author

faddat commented Sep 8, 2022

Think this & the one on 46 are set.

@alexanderbez alexanderbez merged commit 128922c into cosmos:release/v0.45.x Sep 8, 2022
@alexanderbez
Copy link
Contributor

Thanks for all the hard work @faddat 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants