eitsupi commented on issue #46646: URL: https://github.com/apache/arrow/issues/46646#issuecomment-5266155696
Could this actually be a limitation of pre-commit rather than lintr itself? My understanding is that pre-commit may still provision a hook's environment even when no files matching that hook were changed. If so, requiring R for contributors who are not touching the R code would be a consequence of the hook-management model, and perhaps a sign that pre-commit is not an ideal fit for this particular monorepo use case. Have alternatives such as lefthook been considered? Tools in that category typically invoke already-installed commands only when relevant files are involved. I think using jarl can still make sense for other reasons. I am just not sure that avoiding an additional non-Python toolchain dependency is, by itself, the right way to frame this particular problem. -- 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]
