fix: use reverseCheckoutOrder in forcePush

Signed-off-by: Kipras Melnikovas <kipras@kipras.org>

Author: kiprasmel

apply.ts

@@ -25,6 +25,7 @@ export const apply: BranchSequencerBase = (args) =>
 		// callbackAfterDone: defaultApplyCallback,
 		delayMsBetweenCheckouts: 0,
 		behaviorOfGetBranchBoundaries: BehaviorOfGetBranchBoundaries["parse-from-not-yet-applied-state"],
+		reverseCheckoutOrder: false,
 	}).then(
 		(ret) => (markThatApplied(args.pathToStackedRebaseDirInsideDotGit), ret) //
 	);

forcePush.ts

@@ -121,4 +121,16 @@ export const forcePush: BranchSequencerBase = (argsBase) =>
 		 */
 		behaviorOfGetBranchBoundaries:
 			BehaviorOfGetBranchBoundaries["ignore-unapplied-state-and-use-simple-branch-traversal"],
+
+		/**
+		 * (experimental)
+		 *
+		 * github just closed (emptily merged) one of the PRs
+		 * because some commit was now already part of some other branch.
+		 *
+		 * pretty sure that pushing newest branches first, and oldest later,
+		 * instead of the current "oldest first, then newest",
+		 * would solve this.
+		 */
+		reverseCheckoutOrder: true,
 	});

git-stacked-rebase.ts

@@ -299,6 +299,7 @@ export const gitStackedRebase = async (
 						BehaviorOfGetBranchBoundaries[
 							"if-stacked-rebase-in-progress-then-parse-not-applied-state-otherwise-simple-branch-traverse"
 						],
+					reverseCheckoutOrder: false,
 				});
 			} else {
 				/**