Too Long; Didn't Read
<a href="https://teamci.co" target="_blank">TeamCI’s</a> core runs multiple static analysis tools against code and reports back to the <a href="https://blog.github.com/2018-05-07-introducing-checks-api/" target="_blank">GitHub Checks API</a>. Teams use multiple languages, which means tools are written in different languages and released in different ways. TeamCI’s check builder must account for the variety while being flexible enough to adopt new tools and languages. I also wanted empowered users to improve their tools. That’s why the <a href="https://github.com/teamci/builder" target="_blank">check builder</a> is open source. Anyone can throw code on GitHub and label it open source, but that’s not enough context for people to start hacking away. This post walks through the code with examples. Beyond that, it’s just a fun example of what you can get done with elbow grease and spattering of Bash (long live the king).