How’s your capstone going? Hope all is smooth and well! I am sure all of us are setting up our collaboration environment or version control. There’s, of course, dozen of them. In this article, I will focus on Github, which is the one my team uses.
Everyone has their own coding style, and that’s cool. But it can get difficult when collaborating with others, since they also have their own styles. So, how do you set some sort of standards without lifting a finger? Assuming you’re using a version control system like GitHub, the answer is linters. Linters are usually built-in under GitHub Actions, where you need to create a YAML file under ./github/workflows
. (If you’re rusty with GitHub Actions, you can refer to the documentation) Linters can catch things such as undefined functions, unused variables, potential bugs, syntax errors, and funky structures. In summary, they make your code cleaner and easier to read.
Some popular ones include ESLint for JavaScript and Flake8 for Python. Each of these linters requires its own set up. As your codebase gets bigger and more varied, you’ll need to add more and more linters for different types of code. Sounds pretty tiring, right? That’s what the GitHub Services DevOps Engineering team thought, which is why they started their own linter, called the SUPER LINTER. This linter is basically one linter for all linters.
Right now, GitHub Super Linter seems to support popular and standard linters out of the box. There are also advanced options available, allowing you to customize Super Linter to your team’s specific needs. I can’t go into technical details since I personally just discovered this tool a couple days ago while setting up a Continuous Integration environment (CI) for my team. But I highly recommend it – it seems like a must-have for easily managing your Continuous Integration and having clean code!
Let me know what you think and also if there are any other super tools I’m missing out on.
GitHub Super Linter: https://github.com/github/super-linter
Source: https://github.blog/2020-06-18-introducing-github-super-linter-one-linter-to-rule-them-all/
Leave a Reply