Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×
Programming Microsoft

Microsoft's GitHub Offers Open-Source Developers 'One Linter to Rule Them All' (zdnet.com) 33

"GitHub says it's open-sourcing its in-house linting tool, the GitHub Super Linter, to clean up code," reports ZDNet: Having a tool that checks source code for programming blunders and other errors is useful for developers. Now Microsoft-owned GitHub has released the 'Super Linter' to help developers avoid the hassles of setting up code repositories with multiple linters...

GitHub describes it as a "simple combination of various linters, written in bash, to help validate your source code" for the purpose of preventing broken code from being uploaded to a 'master' branch, the key branch that other branches in a tree are merged to... The Super Linter Action lets developers 'lint' or check their code base using popular linters for Python, JavaScript, Go, XML, YAML, and more programming languages. As such, GitHub engineer Lucas Gravley describes the Super Linter as the "one linter to rule them all".

"The GitHub Super Linter was built out of necessity by the GitHub Services DevOps Engineering team to maintain consistency in our documentation and code while making communication and collaboration across the company a more productive experience," says Gravley... "When you've set your repository to start running this action, any time you open a pull request, it will start linting the code case and return via the Status API. It will let you know if any of your code changes passed successfully, or if any errors were detected, where they are, and what they are," explains Gravley.

The Super Linter doesn't fix problems but does flag them, so developers can then go back and fix them before they reach the master branch.

This discussion has been archived. No new comments can be posted.

Microsoft's GitHub Offers Open-Source Developers 'One Linter to Rule Them All'

Comments Filter:
  • by Impy the Impiuos Imp ( 442658 ) on Saturday June 20, 2020 @12:01PM (#60205852) Journal

    As usual, programmers miss the forest for the trees. The problem isn't Lint. It's misuse by management who turn on almost everything, so you get 174,668 warnings that your castings of both sides of an equation to the same type (to prove to lints that the programmer considered the base types) is, ha ha, actually pointless, because the compiler up-promotes both to signed int anyway, and by casting, clearly you don't understand that.

    Dumb programmers of Lint. These violations are not bugs. Develop real tools that find bugs, and design languages with this in mind from the ground up. Lint was a clever exercise...40 years ago. Break free from your entrenched rut.

  • by Dan East ( 318230 ) on Saturday June 20, 2020 @12:09PM (#60205866) Journal

    I'm not convinced this is the right point in the development pipeline to be catching these kinds of issues. Perhaps it is a "failsafe" to catch basic syntax type errors that should have been never been committed in the first place?

    • I'm not convinced this is the right point in the development pipeline to be catching these kinds of issues. Perhaps it is a "failsafe" to catch basic syntax type errors that should have been never been committed in the first place?

      The compiler will (should) catch "basic syntax type errors"; lint is *suppose* to be for flagging ambiguous things that will otherwise/probably pass compilation. Most complaints are about requiring programmers to add things simply to shut lint up.

      Pet peeve: articles/people that say, "invalid syntax error".

    • Typically it's something that happens during code review, when a pull request is made.

      It's kind of convenient, because then the linter catches all style deviations (improper indent?) so code reviewers can focus on more important things.
  • by iggymanz ( 596061 ) on Saturday June 20, 2020 @12:18PM (#60205888)

    Oh you evil sinner who isn't virtue signalling and being PC and worke, don't you know that phrase has been changed to something else?

    Can't remember what, maybe it's "pimp daddy" branch or someshit but you'd better edit that summary

  • ... [lists only joke/scripting/markup languages] and other programming languages.

    There's one big fat hint that I'm not going to use this. :)

  • Can I still write "TL;DR" or do I have to start using "/*NOTREACHED*/" ?

  • Why is GitHub getting involved with processing cotton?

The biggest difference between time and space is that you can't reuse time. -- Merrick Furst

Working...