You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
mega-linter is a tool that we use to check all HTML, Markdown, and Sass files. It currently takes around 3 minutes to run, which is the longest of the 5 initial lint jobs. Since it is run first, it blocks the generate-* and build-website jobs from starting. Increasing the speed of mega-linter would increase the speed of the entire CI.
The slowest part of using mega-linter is not running it, but instead downloading it. It requires downloading a 3.5 GB docker image, which contains a whole host of unused linters.
mega-linter allows using custom flavors, which are slim versions of the default image. If the CI could be configured to use one of those flavors instead, the CI times would be decreased. We currently only use 3 linters, so only they are required:
I additionally asked in Github Discussions how to create a custom flavor of mega-linter that just includes the linters we need. If that's not possible and a provided flavor is not found, it may be worth just installing each linter manually.
The text was updated successfully, but these errors were encountered:
If making our own custom flavor isn't worth it, then I think https://megalinter.io/latest/flavors/javascript/ should work fine. It contains all the things that I think we would use. But like you said manually installing is also viable given how few there is right now.
With #1090 merging, I don't think we need to create a custom flavor. The Javascript one speeds up mega-linter enough for now that it's not worth the effort of maintaining a fork.
mega-linter
is a tool that we use to check all HTML, Markdown, and Sass files. It currently takes around 3 minutes to run, which is the longest of the 5 initial lint jobs. Since it is run first, it blocks thegenerate-*
andbuild-website
jobs from starting. Increasing the speed ofmega-linter
would increase the speed of the entire CI.The slowest part of using
mega-linter
is not running it, but instead downloading it. It requires downloading a 3.5 GB docker image, which contains a whole host of unused linters.mega-linter
allows using custom flavors, which are slim versions of the default image. If the CI could be configured to use one of those flavors instead, the CI times would be decreased. We currently only use 3 linters, so only they are required:bevy-website/.mega-linter.yml
Lines 1 to 4 in cbd158c
I additionally asked in Github Discussions how to create a custom flavor of
mega-linter
that just includes the linters we need. If that's not possible and a provided flavor is not found, it may be worth just installing each linter manually.The text was updated successfully, but these errors were encountered: