You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that we have Github Actions setup, it would be nice if it could also run a code linter on every commits to warn us about common mistakes and keep the code style consistent (indentation, spaces, unused variables etc). A common tool for this task seems to be super-linter (https://github.com/github/super-linter), which also supports Java.
The text was updated successfully, but these errors were encountered:
Exactly! I think it would be best to have this as a separate job next to the Gradle step, so that both jobs, the linting and the tests, are always run even if one of them fails.
Now that we have Github Actions setup, it would be nice if it could also run a code linter on every commits to warn us about common mistakes and keep the code style consistent (indentation, spaces, unused variables etc). A common tool for this task seems to be super-linter (https://github.com/github/super-linter), which also supports Java.
The text was updated successfully, but these errors were encountered: