Codestyle and CI

[kirs]

I'd love to make it easier to contribute to ProxySQL as a project. As someone who recently worked on patches, I found couple things particularly unclear:

• Code style and warnings. There's an extensive list of warnings printed every time you make, which makes you wonder if it's your change that made it unhappy or if it's supposed to be that way.
• Tests and CI. It's not very clear how to run CI locally (I could be wrong but how_to.md is somewhat outdated?) and there's no build triggered automatically once you push commits, which makes the feedback loop very slow. From what I get there's some kind of bot (Automated message: PR pending admin approval for build testing) for project owners but as an external contributor I can't see build results.

I'm curious to see your thoughts about:

• What's the authors view on trying to standardize the codebase and perhaps run clang-tidy or an alternative when merging new code, with the target of having no warnings on build?
• What's the authors view on introducing GitHub Actions for CI? Even if there's another build system used internally at ProxySQL LLC, GitHub Actions will be useful for external contributors. It's completely free for open source projects and it works on forks, which will make it easier to write patches.

I'd be happy to contribute to some of those things if it's something that project authors would like to see.

@renecannao

[kirs]

I just realized there's some work in https://github.com/sysown/proxysql/pull/1969 done already, thoughts on getting some parts of it (whether on Travis CI or GitHub Actions) merged to make the life better for external contributors?

[renecannao]

@pondix , @val214 , @JavierJF : can you please follow up on this?