fix: switch back from native rebase to custom for finding commits, again

actually no need to use native rebase for __finding__ the commits.
for actually rebasing, we're already doing it w/ the native rebase.

for finding commits, using the native rebase had various issues,
it involved having to do other hacks & work-arounds,
and in general didn't represent what we were actually doing,
so e.g. could cause unwanted side-effects, e.g. by calling the
post-rewrite hook, when it's not actually meant to.

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

Author: kiprasmel

git-stacked-rebase.ts

@@ -440,18 +440,18 @@ export const gitStackedRebase = async (
 			initialBranch,
 			currentBranch,
 			// __default__pathToStackedRebaseTodoFile
-			pathToStackedRebaseTodoFile,
-			() =>
-				getWantedCommitsWithBranchBoundariesUsingNativeGitRebase({
-					gitCmd: options.gitCmd,
-					repo,
-					initialBranch,
-					currentBranch,
-					dotGitDirPath,
-					pathToRegularRebaseTodoFile,
-					pathToStackedRebaseTodoFile,
-					pathToRegularRebaseDirInsideDotGit,
-				})
+			pathToStackedRebaseTodoFile
+			// () =>
+			// 	getWantedCommitsWithBranchBoundariesUsingNativeGitRebase({
+			// 		gitCmd: options.gitCmd,
+			// 		repo,
+			// 		initialBranch,
+			// 		currentBranch,
+			// 		dotGitDirPath,
+			// 		pathToRegularRebaseTodoFile,
+			// 		pathToStackedRebaseTodoFile,
+			// 		pathToRegularRebaseDirInsideDotGit,
+			// 	})
 		);
 
 		if (!wasRegularRebaseInProgress || options.viewTodoOnly) {
@@ -1359,6 +1359,7 @@ export async function getWantedCommitsWithBranchBoundariesOurCustomImpl(
 	return extendCommitsWithBranchEnds(repo, bb, wantedCommits);
 }
 
+noop(getWantedCommitsWithBranchBoundariesUsingNativeGitRebase);
 async function getWantedCommitsWithBranchBoundariesUsingNativeGitRebase({
 	gitCmd,
 	repo,