You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It could be nice if backport automatically handled conflicts in yarn.lock files by running yarn (or a custom command like yarn kbn bootstrap) and then git commit --no-edit when it exits successfully.
The text was updated successfully, but these errors were encountered:
backport being a useful tool outside the realm of javascript I'm hesitant to implement something language specific like this.
For a while I've been thinking about changing the project config (.backportrc.json) from json to js. This would allow users to implement pre- and post-backport hooks.
I'm not opposed, but would only want to handle automatic conflict resolution when the files were exactly just yarn.lock, but that happens less and less these days (in my experience) so I don't see it as particularly valuable.
It could be nice if backport automatically handled conflicts in
yarn.lock
files by runningyarn
(or a custom command likeyarn kbn bootstrap
) and thengit commit --no-edit
when it exits successfully.The text was updated successfully, but these errors were encountered: