Hi!
GitLab's Code Quality is a part of its merge request / code review facilities. In order to use it, you upload reports (e.g. like the one generated by CodeNarc) to it and those reports are then presented to the reviewers in a merge request. This takes a very pragmatic approach to this topic: Instead of enforcing strict rules on the acceptable or inacceptable flaws in the code, it gives an overview of new (but also fixed) flaws to help the reviewer. I call this pragmatic, because setting up a ruleset in and of itself is an enormous task, and can easily stall or cripple adoption of a linter.
I'm currently working on a report generator for this. Actually, it's pretty simple and I'm almost finished, just need to clean up and test a bit. Just wanted to present this here up front, perhaps to answer questions and receive suggestions on the matter.
Greetings!
Uli
Hi!
GitLab's Code Quality is a part of its merge request / code review facilities. In order to use it, you upload reports (e.g. like the one generated by CodeNarc) to it and those reports are then presented to the reviewers in a merge request. This takes a very pragmatic approach to this topic: Instead of enforcing strict rules on the acceptable or inacceptable flaws in the code, it gives an overview of new (but also fixed) flaws to help the reviewer. I call this pragmatic, because setting up a ruleset in and of itself is an enormous task, and can easily stall or cripple adoption of a linter.
I'm currently working on a report generator for this. Actually, it's pretty simple and I'm almost finished, just need to clean up and test a bit. Just wanted to present this here up front, perhaps to answer questions and receive suggestions on the matter.
Greetings!
Uli