fix: use VITEST env guard instead of NODE_ENV to prevent silent breakage in customer workflows

Co-Authored-By: Niels Swimberghe <3382717+Swimburger@users.noreply.github.com>

Author: devin-ai-integration[bot]

dist/index.js

@@ -39743,8 +39743,10 @@ async function createPR(octokit, owner, repo, branchName, targetBranch, isFromFe
     core.info(`Pull request created: ${prResponse.data.html_url}`);
     return prResponse;
 }
-// Auto-invoke only when running as the action entry point (not when imported in tests)
-if (process.env.NODE_ENV !== "test") {
+// Auto-invoke only when running as the action entry point (not when imported in tests).
+// Vitest sets VITEST=true automatically; NODE_ENV is not used because a customer's
+// workflow could set NODE_ENV=test and silently prevent run() from executing.
+if (!process.env.VITEST) {
     run();
 }
 

src/sync.ts

@@ -665,7 +665,9 @@ async function createPR(
     return prResponse;
 }
 
-// Auto-invoke only when running as the action entry point (not when imported in tests)
-if (process.env.NODE_ENV !== "test") {
+// Auto-invoke only when running as the action entry point (not when imported in tests).
+// Vitest sets VITEST=true automatically; NODE_ENV is not used because a customer's
+// workflow could set NODE_ENV=test and silently prevent run() from executing.
+if (!process.env.VITEST) {
     run();
 }