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 wrapf warning after Pinning #4172

Merged
merged 1 commit into from
Jul 25, 2023
Merged

Conversation

DimitrisJim
Copy link
Contributor

Description

wonder why the linter is catching this.

closes: #XXXX

Commit Message / Changelog Entry

chore: fix wrapf warning after pinning

see the guidelines for commit messages. (view raw markdown for examples)


Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

  • Targeted PR against correct branch (see CONTRIBUTING.md).
  • Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
  • Code follows the module structure standards and Go style guide.
  • Wrote unit and integration tests.
  • Updated relevant documentation (docs/) or specification (x/<module>/spec/).
  • Added relevant godoc comments.
  • Provide a commit message to be used for the changelog entry in the PR description for review.
  • Re-reviewed Files changed in the Github PR explorer.
  • Review Codecov Report in the comment section below once CI passes.

@crodriguezvega
Copy link
Contributor

wonder why the linter is catching this.

Looks like we need new linters... :trollface:

@DimitrisJim DimitrisJim merged commit f822b4f into feat/wasm-clients Jul 25, 2023
@DimitrisJim DimitrisJim deleted the jim/nit-wrapf-warning branch July 25, 2023 12:44
@faddat faddat mentioned this pull request Sep 10, 2023
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants