Replies: 1 comment
-
|
@mec0202 there are currently both sfdx-scanner and code-analyzer in MegaLinter sfdx-scanner is retired so will be soon retired from MegaLinter, so you can disable the following linters You probably need to add variables related to SALESFORCE_CODE_ANALYZER_* to exclude files instead :) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi sfdx-hardis community,
I investigated that the Mega Linter Execution time (inside of an usual Org Monitoring run (Backup --> Apex Test, Mega Linter, Org Monitoring) executed via Github) is on my side for a quite "empty" org pretty long. The Mega Linter execution time It is always >3h.
I see in the logs, that specially the "code-analyzer-aura" check is here the long running test:
after this long running section

I see that for example:
get here also evaluated and files in this folders are part of the check.
Example:
Is it expected behavior that these files (which are created by sfdx hardis) also part of the check?
I tried to disable the check of specific folders via the following .
mega-linter-ymlfile:Unfortunately this has not solved my issue.
Could you please give me a hint regarding this topic and what is best practice to solve this?
Thank you
Greetings
Beta Was this translation helpful? Give feedback.
All reactions