Open jmeridth opened 7 months ago
Can anybody check out my coding to see if it's of any use at this point wow I've been called a lot of things but never spam I am guaranteeing you I am not spam in any shape way or form I actually have a legit question I just didn't know how to ask it correctly anyway so I don't know anything about coding and somehow I am able to grasp the concept and I may have some good opportunities to share my discoveries
Is your feature request related to a problem?
Currently we use a
make lint
target to run linting locally in each of our OSPO GitHub Actions (example). This "works" but does not cover the larger list of linters that super-linter runs against our code in our linting workflow on each OSPO GitHub Action (example).The issue is that super-linter does not work well on arm64 architecture (Apple M1, for example). There is an open PR trying to work through this.
Related OSPO Tool
automatic-contrib-prs GitHub Action, cleanowners GitHub Action, contributors GitHub Action, evergreen GitHub Action, issues-metrics GitHub Action, stale-repos GitHub Action
Describe the solution you'd like
We spin up a super-linter container and run linting against the local code
Describe alternatives you've considered
Current: Makefile calling individual tools to try to match the large lister of linters built into super-linter and run in our linting workflow on each OSPO GitHub Action
Additional context
We have people subscribed to the super-linter PR and will try this out as soon as that is merged.