ci: disable npm lint, as we don't make use of its results right now #28
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.
As mentioned in #19 I find it pretty hard to work with PRs because of those unrelated warnings, which show up on every PR. Even though no changes have been made on those files.
My proposal here is to either merge this PR and disable this step for now, until we find some time to fix those warnigns. Or find a switch for "warnings as errors" and fail the build in the case of violations.
Spamming PRs and not using the outcome to improve the code seems counterproductive.