-
Notifications
You must be signed in to change notification settings - Fork 1
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(execa): use await execa
instead of execaSync
since it produces unexpected errors when spawning git commands - fixes #17
#25
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #25 +/- ##
==========================================
- Coverage 91.40% 90.09% -1.31%
==========================================
Files 12 12
Lines 989 1030 +41
==========================================
+ Hits 904 928 +24
- Misses 85 102 +17 ☔ View full report in Codecov by Sentry. |
b150547
to
212ae4f
Compare
await execa
instead of execaSync
since it produces unexpected errors when spawning git commands - fixes #19await execa
instead of execaSync
since it produces unexpected errors when spawning git commands - fixes #17
Hi @syphernl, is it OK on your end with this code ? I'm gonna add the debug logs in another commit. |
Uses most of produced code from here #24 |
…s unexpected errors when spawning git commands - fixes #17 Co-authored-by: syphernl <syphernl@users.noreply.github.com> Signed-off-by: kilianpaquier <kilian@kilianpaquier.com>
212ae4f
to
f42bfef
Compare
Applied these changes on my test env, no |
Great, I'm gonna add debug logs and check this |
Signed-off-by: kilianpaquier <kilian@kilianpaquier.com>
3545245
to
3330d70
Compare
🎉 This issue has been resolved in version v1.4.0 🎉 |
Fixes both #17 and #20