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
this might may be not impact the source code of oca-port directly, but I would like to make sure you guys heard about the mergiraf git conflict resolution tool. From my little testing mergiraf is REALLY AWESOME, like may be it's fixing 80% or more of the git conflicts I usually encounter while doing ports in the OCA...
I proposed some initial Python support here https://codeberg.org/mergiraf/mergiraf/pulls/44
You can test my branch by checking it out and doing cargo build; cargo install --path .
So far it worked great for me...
So for oca-port, the whole point will be ensuring the computer where oca-port will run will have mergiraf configured (if that's on an OCA bot for instance). As it will automate most of the git cherry-pick command which have conflicts. This is really something that made me have much more faith we will be able to have effective commit porting bots in the OCA...
The text was updated successfully, but these errors were encountered:
That's really something I would like to see one day: a GH Action responsible to automatically port changes, the pain point was indeed the resolution of conflicts which wouldn't make this feature working very often.
We have to look at mergiraf then, thanks for the hint!
FYI oca-port is doing git format-patch, not git cherry-pick, I don't know if it's an issue for tools like mergiraf as we play with intermediate patches, not commits. To test...
Hello,
this might may be not impact the source code of oca-port directly, but I would like to make sure you guys heard about the mergiraf git conflict resolution tool. From my little testing mergiraf is REALLY AWESOME, like may be it's fixing 80% or more of the git conflicts I usually encounter while doing ports in the OCA...
I proposed some initial Python support here https://codeberg.org/mergiraf/mergiraf/pulls/44
You can test my branch by checking it out and doing cargo build; cargo install --path .
So far it worked great for me...
So for oca-port, the whole point will be ensuring the computer where oca-port will run will have mergiraf configured (if that's on an OCA bot for instance). As it will automate most of the git cherry-pick command which have conflicts. This is really something that made me have much more faith we will be able to have effective commit porting bots in the OCA...
The text was updated successfully, but these errors were encountered: