sils

FWIW the default thing is actually https://i.imgur.com/JO0nXL7.png

This table is our aggregated view that gets triggered if there's a lot of comments that would spam the PR.

The code review functionality is completely open source at code.gitmate.io FWIW.

We grew from the whole review thing into automation for PRs (setting lots of labels for PRs automatically, managing review queues; it's all in GitMate) and eventually started with issues. Our next step is to split the review and issues because this is becoming very hard to communicate marketing wise ;)

Hey, would it help you if we were to include https://github.com/fukamachi/sblint in coala? Do you know other tools? We could easily integrate them using https://api.coala.io/en/latest/Developers/Writing_Linter_Bea... if there's concrete interest

coala always leaves you in control, you can tell it to e.g. show a patch before applying. If you explicitly configure it you can set it to automatically apply patches that are coming from certain analysis routines.

So ATM the only way to get more info about a bear is by querying coala for it: `coala -B -b=AlexBear`

We have a project in planning stage to make a browsable webpage generated from the per bear documentation, we will also look a lot at the configurability and documentation of the individual bears for the next release.

Hey, upgrading pip should solve your issue.

I filed an issue for the missing info at https://github.com/coala-analyzer/website/issues/30 , thank you for your feedback!

One of our awesome contributors wrote a little tool that makes it easy to script such videos, the video is updated on the website (readme will come soon) and script available and patchable on https://github.com/hypothesist/termtype/blob/master/coala_in...

Your comment? We love constructive feedback, thanks a lot :)

Oh btw. coala allows automatic fixes for source code, most tools like code climate are usually reporting only and can be more annoying than helpful.

Thanks, I've filed an issue at https://github.com/coala-analyzer/website/issues/27 . We'll definitely look at that. You probably know how manpower in open source projects with no commercial backing behaves :)

Good suggestion, I've created a FAQ stub and we're tracking this here if you're interested in how this goes: https://github.com/coala-analyzer/website/issues/22

Thanks!

Thanks, I added a link right on top of http://coala-analyzer.org/ to clarify it a bit. The website isn't particularly good, we're working on a new one which provides lots of cool things and better information, probably implemented by a GSoC student.

Indeed. coala is more of a framework that allows you to plug in any analysis routine. However, it also provides means to create new code analysis very easily and combine arbitrary routines.

So yes, there are some very simple generic algorithms (line length checking, spacing corrections, we have things like variable name checking in the works which only need a few lines "language definition") and you can combine them with - possibly wrapped or not - language dependent algorithms easily.

This is useful for the user because he doesn't have to learn and configure tons of tools and he has some basic functionality for every language - even the ones he writes tomorrow.

It's also useful for people writing static code analysis because they can just write their algorithm and be done with it - why should everybody rewrite a CLI interface, editor plugins and so on?

I wrote a thesis about code clone detection (another algorithm that is basically generic and would need only a relatively small parsing part per language, coala allows me to modularize meanfully into parsing and language independent AST processing) and it just took me a few functions that actually performed the analysis. People can now use it easily which usually isn't true for research programs and I had even less work than I would have if I had written it without coala.