mattcasters commented on issue #3103: URL: https://github.com/apache/hop/issues/3103#issuecomment-3641274643
I remember writing these "code quality" checks in a previous tool without too much success. On the other hand, if I didn't agree with this issue, I wouldn't have written it in the past :-) Perhaps it's worth thinking about where this should live: as a `hop` sub-command (`hop qa`) and an action, tied to a project, a folder structure, ...? Do we want the rules to be 'scriptable' to cover non-trivial scenarios? How do we want to run the QA checks: gitlab actions, Jenkins pipeline, Sonar, ...? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
