On second thought, I do not like this approach because it's asking `pub` questions it has already answered for each file, coupled with the fact that `|| true` means pub can fail for whatever reason. Looking at the other linters, and looking at the recent bug report in #120 I think it's safe to assume that pub, or any package manager can be called as a first step and then proceed to super lint.
- add `pub get || true`
- add --fatal flags to throw 1 on exit
Adding `pub get` enables dart to import dev/project dependencies before
analysis/linting. It is set to always return true in the event this has
already occured somewhere else in the CI workflow a pubspec.yaml does not
exist
Using `--fatal-(infos|warnings)` allows super-linter to fail when a lint
is reported.
* upstream/master: (149 commits)
rm dupe end brackets
fix botched merge
fixed docker bug
fixing insta;;
hunting a bug
adding some small cleanup
Bump Actions-R-Us/actions-tagger from v2.0.0 to v2.0.1
Bump actions/github-script from v2.3.1 to v2
Add HTML support to super-linter
Remove ARM_TTK_VERSION from ENV in Dockerfile
Remove noise from ARG in Dockerfile
Minor fix(1) for TestCodebase [ARM]
Minor fix for TestCodebase [ARM]
Update ARM Test Cases readme
Minor updates following merge from upstream/master
Minor bugfixes
Test case updates
Add `editorconfig-checker`
Typo
Use full version numbers for GHA Dependabot will update these automatically
...
- use analysis_options.yaml file (dart convention), mv .dart-lint.yml
- add --fatal-infos switch for testing
- add VALIDATE_DART, because I missed it before
