diff --git a/dist/index.js b/dist/index.js
index bf2f140..1acc2c4 100644
--- a/dist/index.js
+++ b/dist/index.js
@@ -25924,9 +25924,11 @@ async function main(sourceRepoId, targetRepoId, dryRun, tokenForTargetRepo) {
     // only been alive so many years - there's a hard limit on the rate of code I could possibly have generated, which
     // is small compared to, y'know, _companies_. And I don't see organizations of that size caring about GitHub
     // contribution history at whole-org scale - and if they do, it'd be proportionally simple for them to implement it.
+    console.log(`DEBUG - getting source commit history`);
     const sourceCommitHistory = (0, git_1.getNLatestCommits)(SOURCE_DIR, 10);
     // Calling `doSomethingTo(sourceCommitHistory.reverse()); doSomethingElseTo(sourceCommitHistory.reverse());` results
     // in the second invocation receiving the double-reversed array.
+    console.log(`DEBUG - reversing source commit history`);
     const reversedSourceCommitHistory = sourceCommitHistory.reverse();
     // Only have to go back far enough in target history to find the commit that immediately precedes the oldest
     // commit in source history
@@ -25936,7 +25938,9 @@ async function main(sourceRepoId, targetRepoId, dryRun, tokenForTargetRepo) {
     // than abandoning the target tree after the insertion point and trusting in later operation to rebuild it - because
     // the target repo's tree will have representations of commits from _other_ (source)repos too, which we cannot
     // recreate without their context)
+    console.log(`DEBUG - getting target commit history`);
     let targetCommitHistory = (0, git_1.getCommitsSinceLatestBeforeGivenDate)(TARGET_DIR, reversedSourceCommitHistory[0].date);
+    console.log(`DEBUG - iterating over source commit history`);
     for (const sourceCommit of reversedSourceCommitHistory) {
         // "(Index of) First Target Commit that is earlier than (or equal to) the source commit"
         const targetCommitIndex = targetCommitHistory.findIndex(c => c.date <= sourceCommit.date);
diff --git a/node_modules/@vercel/ncc/dist/ncc/cli.js.cache b/node_modules/@vercel/ncc/dist/ncc/cli.js.cache
index 8d26689..9b80e5f 100644
Binary files a/node_modules/@vercel/ncc/dist/ncc/cli.js.cache and b/node_modules/@vercel/ncc/dist/ncc/cli.js.cache differ
diff --git a/node_modules/@vercel/ncc/dist/ncc/index.js.cache b/node_modules/@vercel/ncc/dist/ncc/index.js.cache
index 71a7f90..0a363fb 100644
Binary files a/node_modules/@vercel/ncc/dist/ncc/index.js.cache and b/node_modules/@vercel/ncc/dist/ncc/index.js.cache differ
diff --git a/node_modules/@vercel/ncc/dist/ncc/loaders/relocate-loader.js.cache b/node_modules/@vercel/ncc/dist/ncc/loaders/relocate-loader.js.cache
index a5dba6e..2536764 100644
Binary files a/node_modules/@vercel/ncc/dist/ncc/loaders/relocate-loader.js.cache and b/node_modules/@vercel/ncc/dist/ncc/loaders/relocate-loader.js.cache differ
diff --git a/node_modules/@vercel/ncc/dist/ncc/loaders/shebang-loader.js.cache b/node_modules/@vercel/ncc/dist/ncc/loaders/shebang-loader.js.cache
index 0b4b098..9dca606 100644
Binary files a/node_modules/@vercel/ncc/dist/ncc/loaders/shebang-loader.js.cache and b/node_modules/@vercel/ncc/dist/ncc/loaders/shebang-loader.js.cache differ
diff --git a/node_modules/@vercel/ncc/dist/ncc/loaders/ts-loader.js.cache b/node_modules/@vercel/ncc/dist/ncc/loaders/ts-loader.js.cache
index 4272069..44af893 100644
Binary files a/node_modules/@vercel/ncc/dist/ncc/loaders/ts-loader.js.cache and b/node_modules/@vercel/ncc/dist/ncc/loaders/ts-loader.js.cache differ
diff --git a/src/main.ts b/src/main.ts
index 36b0c20..85590a5 100644
--- a/src/main.ts
+++ b/src/main.ts
@@ -29,10 +29,12 @@ export async function main(sourceRepoId: RepoId, targetRepoId: RepoId, dryRun: b
     // only been alive so many years - there's a hard limit on the rate of code I could possibly have generated, which
     // is small compared to, y'know, _companies_. And I don't see organizations of that size caring about GitHub
     // contribution history at whole-org scale - and if they do, it'd be proportionally simple for them to implement it.
+    console.log(`DEBUG - getting source commit history`);
     const sourceCommitHistory = getNLatestCommits(SOURCE_DIR, 10);
     
     // Calling `doSomethingTo(sourceCommitHistory.reverse()); doSomethingElseTo(sourceCommitHistory.reverse());` results
     // in the second invocation receiving the double-reversed array.
+    console.log(`DEBUG - reversing source commit history`);
     const reversedSourceCommitHistory = sourceCommitHistory.reverse();
     // Only have to go back far enough in target history to find the commit that immediately precedes the oldest
     // commit in source history
@@ -42,8 +44,10 @@ export async function main(sourceRepoId: RepoId, targetRepoId: RepoId, dryRun: b
     // than abandoning the target tree after the insertion point and trusting in later operation to rebuild it - because
     // the target repo's tree will have representations of commits from _other_ (source)repos too, which we cannot
     // recreate without their context)
+    console.log(`DEBUG - getting target commit history`);
     let targetCommitHistory = getCommitsSinceLatestBeforeGivenDate(TARGET_DIR, reversedSourceCommitHistory[0].date);
 
+    console.log(`DEBUG - iterating over source commit history`);
     for (const sourceCommit of reversedSourceCommitHistory) {
         // "(Index of) First Target Commit that is earlier than (or equal to) the source commit"
         const targetCommitIndex = targetCommitHistory.findIndex(c => c.date <= sourceCommit.date);