kilianpaquier / semantic-release-backmerge

Backmerge feature for semantic-release with automatic PR creation when a conflict is identified. Available for Github, Gitlab, Bitbucket and Gitea
https://www.npmjs.com/package/@kilianpaquier/semantic-release-backmerge
MIT License
3 stars 1 forks source link

fix(execa): use `await execa` instead of `execaSync` since it produces unexpected errors when spawning git commands - fixes #17 #25

Closed kilianpaquier closed 1 month ago

kilianpaquier commented 1 month ago

Fixes both #17 and #20

codecov[bot] commented 1 month ago

Codecov Report

Attention: Patch coverage is 64.08451% with 51 lines in your changes missing coverage. Please review.

Project coverage is 90.09%. Comparing base (29c7f75) to head (3330d70). Report is 4 commits behind head on main.

Files with missing lines Patch % Lines
lib/git.ts 29.26% 29 Missing :warning:
lib/pull-request.ts 8.33% 22 Missing :warning:
Additional details and impacted files ```diff @@ 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 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

kilianpaquier commented 1 month ago

Hi @syphernl, is it OK on your end with this code ? I'm gonna add the debug logs in another commit.

kilianpaquier commented 1 month ago

Uses most of produced code from here https://github.com/kilianpaquier/semantic-release-backmerge/pull/24

syphernl commented 1 month ago

Hi @syphernl, is it OK on your end with this code ? I'm gonna add the debug logs in another commit.

Applied these changes on my test env, no git errors regarding ENOENT anymore so in that regard it seems to be working. Still getting the "Updates were rejected because the tip of your current branch is behind" but that will be handled in #23

kilianpaquier commented 1 month ago

Great, I'm gonna add debug logs and check this tip issue afterhand but in another PR

github-actions[bot] commented 1 month ago

🎉 This issue has been resolved in version v1.4.0 🎉