-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Mega-Linter #16
Add Mega-Linter #16
Conversation
nvuillam
commented
Dec 26, 2020
- Activate Mega-Linter as a Github action workflow
- Add info in README
Codecov Report
@@ Coverage Diff @@
## main #16 +/- ##
=======================================
Coverage 73.61% 73.61%
=======================================
Files 2 2
Lines 72 72
=======================================
Hits 53 53
Misses 19 19 Continue to review full report at Codecov.
|
bd866e0
to
ff3603c
Compare
ff3603c
to
b645765
Compare
I have evaluated MegaLinter on its merits, but I don't think it is the solution I want to use for linting on this project. |
At the moment, I don't want to take on all that overhead. If I do want to adopt some/all of that tooling, I'd rather manage the dependencies in my own manifest as far as possible for the same reasons I prefer to do that with eslint. As I say, its a matter of taste. |
Your repo = your choice, no problem ;) |
@chris48s would you agree if I let just the README part ? Just to have a hearth here :p https://nvuillam.github.io/mega-linter/all_linters/ And if you can star the repo, and you're an angel :) |
I have noted that you are on a mission to try and promote MegaLinter via other people's READMEs with PRs like these:
While I wish you luck with your project and some project authors may accept your PRs, I don't plan to recommend any projects I don't use myself here. |
A guy has to try ;) But no problem, my efforts are starting to pay, it's slowly taking off, usually with people deceived by super-linter ^^ Have a nice evening 🥳 |