-
Notifications
You must be signed in to change notification settings - Fork 48
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
Import mega-linter.yml #678
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
mmm, the linter code does not pass linting 🤔
Looking at configuring megalinter, I tend to like a lot how it's easy to identify how to configure or disable linters, there is a direct link in the test output to the megalinter documentation for a given linter, providing information on the linter home page, it's configuration and so on, such as: https://megalinter.io/v6/descriptors/copypaste_jscpd/ It's very convenient. |
It finally works 🎉 :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What will happen to the super-linter? do we keep it also?
I was expecting to still keep it for some time, till we have more experience and can drop one of the two |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, let's try it
Import mega-linter.yml, to test mega-linter.
Include file mentioend at https://megalinter.io/latest/install-github/, but at least currently, do not commit directly to the PR, but create a new PR, to be tested/reviewed.
Fix #147.