When cherry-pick conflict cannot be resolved about git-backporting HOT 2 CLOSED

Hi @Yaminyam, thanks for raising this question!

The limitation of this tool actually matches the limitation of the cherry-pick git command when talking about conflicts resolution, I tried to make the toolt as configurable and flexible [1] as possible such that you can set the merge strategy that fits better your use case (from those listed in the git documentation [2]).

Given that, if you are in a situation where an automated conflict resolution cannot be applied the only way I can see it is to consider that as an outlier, i.e., in such cases we were used to manually create the cherry-picked pull/merge request.

So my suggestion is to use the default merge strategy that works better for most of your use cases and change it for those cases where that was not good enough (or use the manual/raw approach to cherry-pick that commit(s)).

I hope I have fully answered your question, if not feel free to add more details 🚀

[1] https://github.com/kiegroup/git-backporting?tab=readme-ov-file#default-cherry-pick-strategy
[2] https://git-scm.com/docs/git-cherry-pick#Documentation/git-cherry-pick.txt---strategyltstrategygt

from git-backporting.

Thank you for your kind reply.
I am also implementing backport automation, and I asked this question because I thought you would be familiar with it because I have experienced related problems.
If cherry-pick fails, I'm thinking of handling it manually by leaving a comment in the original pr.

from git-backporting.