GutHub has released Super Linter, with the intention of making it easier to prevent broken code getting into your master branches.

The GitHub team Super Linter was created by the GitHub Services DevOps Engineering team because they found it difficult to maintain consistency in documentation and code. In addition to preventing broken code from being uploaded to the default branch, the team also hopes it will help establish coding best practices across multiple languages; build guidelines for code layout and format; and automate the process to help streamline code reviews.

The Super Linter is a source code repository containing a number of existing open source linters that are packaged into a Docker container and called by GitHub Actions. This means that any repository on GitHub.com can call the Super Linter and start using it. The team says it currently supports "a lot of languages and more coming in the future". The list is already extensive with languages ranging from Ansible to YAML and including Clojure, CoffeeScript,  Golang, JavaScript, JSON, Kotlin, Perl, PHP, Python, Ruby, TypeScript and XML.

The way it works is that when you’ve set your repository to start running this action, whenever you open a pull request it starts linting the code and returns the results via the Status API. It reports either that your code changes passed successfully, or the details of any errors detected, where they are, and what they are. You can then go back and fix the problems, create a new push to the open pull request, and  Super Linter will repeat the exercise. You can configure your branch protection rules to make sure all code must pass before being able to merge as an additional measure. 

More Information

Super Linter On GitHub

Related Articles

ESLint Adds ES2020 Support

GitHub Actions API Enters Public Beta 

GitHub Desktop 2.5 Adds Tags

To be informed about new articles on I Programmer, sign up for our weekly newsletter, subscribe to the RSS feed and follow us on Twitter, Facebook or Linkedin.

Comments

Make a Comment or View Existing Comments Using Disqus

or email your comment to: comments@i-programmer.info