yangjunhan commented on pull request #17711: URL: https://github.com/apache/flink/pull/17711#issuecomment-996390103
> I think this will confuse the majority of developers as most do not work on the UI. Can we do something to restore the old behavior of not producing output unless the commit contains changes to the UI? @Airblader There is such output because "flink-runtime-web" is introducing **husky + lint-staged** for linting which essentially uses git hook through pre-commit, and the pre-commit is at the repo level. One way I can think of to restore the older behavior is triggering npm script lint-staged only when `git diff --cached --quiet -- "flink-runtime-web/web-dashboard/*"` (maybe written in an independent shell script). Could you think of any other better way to achieve so? -- 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]
