-
-
Notifications
You must be signed in to change notification settings - Fork 425
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
fix: resolve matched files to cwd instead of gitDir before adding #857
Conversation
Need to normalize the asserted path in tests for the Windows test. |
Because the set of matched files are collected from generated tasks, when using the `relative` options they are relative to the current cwd, not the git dir which might be different.
@okonet I split into two commits because there was technically another fix in there. EDIT: argh, one more test, one more missing normalize. |
@okonet it seems the Appveyor test is failing to something not-test-related. Can you re-trigger it manually somehow? |
I just did but it's still failing with the same message:
There is no information behind this link... Ideas? Can it be Node 14? |
Okay I restarted the whole build and now it seem to work: https://ci.appveyor.com/project/okonet/lint-staged |
@iiroj let me know if that's good to merge and I'll merge it since the check wasn't picked up here but it's all green now. |
@okonet thanks, please do! A merge commit would be better to preserve both fixes in the changelog. |
🎉 This PR is included in version 10.2.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
still not fixed but git is trying to add
|
What, I set it to resolve to absolute paths... 🤔 Let me see again. EDIT: LOL, found the issue. This PR fixed it for the case where |
@Ramesh-Yadav I opened #858 to hopefully fix it for good! |
Because the set of matched files are collected from generated tasks, when using the
relative
options they are relative to the current cwd, not the git dir which might be different.