We had a similar issue in reno that we were able to fix using git's topological sorting, which ensures that a patch does not appear in the log output until the point where it is actually merged.
We had a similar issue in reno that we were able to fix using git's topological sorting, which ensures that a patch does not appear in the log output until the point where it is actually merged.