-
Notifications
You must be signed in to change notification settings - Fork 220
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for relative roots/monorepos #72
Comments
#38 ref |
+1 for this issue. It's a huge pain to use eslint in monorepo now. |
I give it a try in followng week |
I'd really like to start using lefthook and this is a roadblock for us. |
@sHooKDT makes I few changes for monorepos(big thanks), also root path in 0.6.5 now always related to git top.
|
I used @Arkweid's guidance to implement this in #98.
|
I'll try to get to this today,
Thanks!
…On Thu., Dec. 12, 2019, 04:53 Abroskin Alexander, ***@***.***> wrote:
@sHooKDT <https://github.com/sHooKDT> @dflock <https://github.com/dflock>
@ffloyd <https://github.com/ffloyd>
It would be great if someone will also check PR for existing project
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#72>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAALVDFMHUWACHH2DXZPNS3QYIX57ANCNFSM4ISL7L7A>
.
|
Support relative roots for monorepos (#72)
Supoprt for monorepos released in v0.7.0, thanks @jsmestad |
Is there some documentation on how how to use Lefthook in monorepos? |
For example, when you working with monorepo you may want to have config like this:
Possible
root
option behaviour:{staged_files}
should return paths relative to provided root pathfiles
should use root path as working dirrun
should use root path as working dirThe text was updated successfully, but these errors were encountered: