This strategy seems to work every time (at least twice so far) a conflict arises when Camelus is trying to merge new commits + transformations to the 2.0 format to the 2.0.0 branch.
I couldn't find the merge command in the code so I'm not sure how to incorporate this but here are my two cents.
This strategy seems to work every time (at least twice so far) a conflict arises when Camelus is trying to merge new commits + transformations to the 2.0 format to the 2.0.0 branch. I couldn't find the merge command in the code so I'm not sure how to incorporate this but here are my two cents.
See #11943 or https://github.com/ocaml/opam-repository/pull/11877#issuecomment-384943910 for instance