|GitHub Introduces Super Linter|
|Written by Kay Ewbank|
|Tuesday, 30 June 2020|
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 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.
or email your comment to: email@example.com
|Last Updated ( Tuesday, 30 June 2020 )|