-
Notifications
You must be signed in to change notification settings - Fork 335
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
Linting on generated code #39
Comments
mimatache
added a commit
to mimatache/go-blueprint
that referenced
this issue
Nov 9, 2023
mimatache
added a commit
to mimatache/go-blueprint
that referenced
this issue
Nov 10, 2023
mimatache
added a commit
to mimatache/go-blueprint
that referenced
this issue
Nov 11, 2023
mimatache
added a commit
to mimatache/go-blueprint
that referenced
this issue
Nov 12, 2023
Melkeydev
pushed a commit
that referenced
this issue
Nov 12, 2023
* ci: linting on generated code resolve #39 * ci: use golangci-lint action with working-directory * ci: add manual trigger for workflow
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
PR #28 adds a workflow for linting the cli code but this does not lint the template code since that is just a string in the go code. Maybe it would be nice to have CI generate all templates to run the linter on those as well. That users don't have to manually check the generated code with the linter.
The text was updated successfully, but these errors were encountered: