Set up linting #14
Merged
Set up linting #14
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
Author
|
I'm requesting review so that you have a chance to make comments on the lint rules I've picked, the tsconfig.json changes, and the linter script itself. Of course, don't feel the need to look through every source code change I made to satisfy the linter. Most of them are minimal. |
Collaborator
|
Looks reasonable 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR sets up linting for TypeScript (ESLint), shell script (shellcheck), Dockerfiles (hadolint), and Go (golangci-lint).
I also created a workflow that runs Trivy to scan for vulnerabilities in our dependencies. It works for Node.js and Go modules.