✨Thanks to the people who watched the video live with me!✨ Let me know if you want me to cover the other scenarios of using the Super Linter outside of GitHub. And check the other video about linting in general, here: ua-cam.com/video/HDQXWr5TOnI/v-deo.html
While I love the idea of the concept in of itself, I am concerned with how it seems to lack IDE extensions (e.g., VSCode, IntelliJ, Neovim) to perform its lints in real-time, which is crucial in order to optimize developer productivity. The idea is to catch all this as you're working BEFORE it even enters the CI/CD; the CI/CD pipeline (in the case of linters & formatters) is meant to catch any stragglers or anything that may have been overlooked.
You are right, it would be nice to have it as IDE integration. But you can actually run it outside of GH Actions, on your machine... because it run in container or in CLI :)
@@CoderDave I thought about that by attaching it to a pre-commit, but you would still be required to have the container running all the time -- ran into the same issue with git secrets -- but it's still not as productive as having an IDE integration. I've been looking into Mega Linter and Trunk for that reason.
Well, while I understand that the output is not the most user-friendly thing, it is definitely not meaningless. If you know how to read it, it gives you a lot of useful information
@@CoderDave I agree now, but when I was simply trying to get a simple pull request done and there was no apparent instructions on how to read the logs.. Trying a series of 10 different changes to make something happy that had no manual i could find.. It was a huge waste of time. I actually came to this video when trying to figure out how to read the logs. Eventually, I felt defeated, and tired enough to slow down. take a few deep breaths and consider the linter as if it was something that I had to develop myself, and how I might have formatted the logs and how I might expect them to be used. Then it became clear. It's just, as someone who has multiple projects, and very minimal income, taking a deep breath can often feel like a luxury I just can't take.
@CoderDave Nope I change my mind again. Useless it just spit out hundreds of lines it wants to me to manually change based on someone else's style preferences. Complete nonsense. Surely there is just some plugin for pycharm that will auto format my code the way this picky time wasting linter wants it?
A linter is just that, validates your syntax etc and lets you know everything that is not "right" accordingly to the language best practices and pre-defined rules. It is mostly not "someone else's style preferences", the rules are generally accepted in the community for that specific language as best practices. You can change the rules and add/remove checks using the config file. If you want something that automatically format your files, then you need to use a refactoring tool... which is a completely differen\et thing than a linter...
@@CoderDave I mean.. I would say that reading code, is a skill as much as writing code is a skill. I can read code formatted one way or the other, it doesn't matter so much. I have a whole lot of practice from reading code in different languages (as a hobby) for 20+ years. Why should I be required to write code to some unnatural (to me) style, just to avoid forcing people with less skill reading code to expand their mind? We are striving for greatness right? not mediocrity? If I'm mentoring someone and they just can not read my code unless it superlinted with no warnings/errors ... then I have to ask my self.. how hard are they trying? IF we all use the same coding style then the parameter space we are searching for better styles is minimal.. lets explore space.. parameter space! lol
✨Thanks to the people who watched the video live with me!✨
Let me know if you want me to cover the other scenarios of using the Super Linter outside of GitHub. And check the other video about linting in general, here: ua-cam.com/video/HDQXWr5TOnI/v-deo.html
*I will be answering your questions live during the premiere!*
While I love the idea of the concept in of itself, I am concerned with how it seems to lack IDE extensions (e.g., VSCode, IntelliJ, Neovim) to perform its lints in real-time, which is crucial in order to optimize developer productivity.
The idea is to catch all this as you're working BEFORE it even enters the CI/CD; the CI/CD pipeline (in the case of linters & formatters) is meant to catch any stragglers or anything that may have been overlooked.
You are right, it would be nice to have it as IDE integration. But you can actually run it outside of GH Actions, on your machine... because it run in container or in CLI :)
@@CoderDave I thought about that by attaching it to a pre-commit, but you would still be required to have the container running all the time -- ran into the same issue with git secrets -- but it's still not as productive as having an IDE integration. I've been looking into Mega Linter and Trunk for that reason.
Great video! Will be helpful to show how to run this action locally. Thank you
Thanks. Do you mean run the GitHub SuperLinter locally?
@@CoderDave Yes
Can you please create a GitHub action on CD
I’ve already have videos on my channel about that 😄
@@CoderDave can you please help me with links
Thanks Dave 😉
Very welcome
Fantastic video. Extremely helpful. Thank you.
Thanks, happy it was useful
Excellent
Glad you liked it
Became big fan of u
Hehe thanks
Is there anything similar for Gitlab?
Not that I'm aware of. You could modify the source code to make this run with GitLab tho, but I;m not sure how hard it would be to do so
yes :) oxsecurity.github.io/megalinter/latest/installation/#gitlab-ci
Github super linter provides arcane useless output that is mostly meaningless.
Well, while I understand that the output is not the most user-friendly thing, it is definitely not meaningless. If you know how to read it, it gives you a lot of useful information
@@CoderDave I agree now, but when I was simply trying to get a simple pull request done and there was no apparent instructions on how to read the logs.. Trying a series of 10 different changes to make something happy that had no manual i could find.. It was a huge waste of time. I actually came to this video when trying to figure out how to read the logs.
Eventually, I felt defeated, and tired enough to slow down. take a few deep breaths and consider the linter as if it was something that I had to develop myself, and how I might have formatted the logs and how I might expect them to be used. Then it became clear. It's just, as someone who has multiple projects, and very minimal income, taking a deep breath can often feel like a luxury I just can't take.
@CoderDave
Nope I change my mind again. Useless it just spit out hundreds of lines it wants to me to manually change based on someone else's style preferences. Complete nonsense. Surely there is just some plugin for pycharm that will auto format my code the way this picky time wasting linter wants it?
A linter is just that, validates your syntax etc and lets you know everything that is not "right" accordingly to the language best practices and pre-defined rules. It is mostly not "someone else's style preferences", the rules are generally accepted in the community for that specific language as best practices.
You can change the rules and add/remove checks using the config file.
If you want something that automatically format your files, then you need to use a refactoring tool... which is a completely differen\et thing than a linter...
@@CoderDave I mean.. I would say that reading code, is a skill as much as writing code is a skill. I can read code formatted one way or the other, it doesn't matter so much. I have a whole lot of practice from reading code in different languages (as a hobby) for 20+ years. Why should I be required to write code to some unnatural (to me) style, just to avoid forcing people with less skill reading code to expand their mind?
We are striving for greatness right? not mediocrity? If I'm mentoring someone and they just can not read my code unless it superlinted with no warnings/errors ... then I have to ask my self.. how hard are they trying? IF we all use the same coding style then the parameter space we are searching for better styles is minimal.. lets explore space.. parameter space! lol