From b86e7bc54d1c580848bc7a19efe4e79af505aaa0 Mon Sep 17 00:00:00 2001
From: Michael Lively <milively@microsoft.com>
Date: Fri, 29 Sep 2023 11:22:45 -0700
Subject: [PATCH] fix nb codeactions running on autosave when set `true` [main]
 (#194502)

fix nb codeactions running on autosave when set `true`
---
 .../browser/contrib/saveParticipants/saveParticipants.ts       | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/src/vs/workbench/contrib/notebook/browser/contrib/saveParticipants/saveParticipants.ts b/src/vs/workbench/contrib/notebook/browser/contrib/saveParticipants/saveParticipants.ts
index 574945c4f87..1195c7767b2 100644
--- a/src/vs/workbench/contrib/notebook/browser/contrib/saveParticipants/saveParticipants.ts
+++ b/src/vs/workbench/contrib/notebook/browser/contrib/saveParticipants/saveParticipants.ts
@@ -329,7 +329,8 @@ class CodeActionOnSaveParticipant implements IStoredFileWorkingCopySaveParticipa
 		if (context.reason === SaveReason.AUTO) {
 			// currently this won't happen, as vs/editor/contrib/codeAction/browser/codeAction.ts L#104 filters out codeactions on autosave. Just future-proofing
 			// ? notebook CodeActions on autosave seems dangerous (perf-wise)
-			saveTrigger = 'always';
+			// saveTrigger = 'always'; // TODO@Yoyokrazy, support during debt
+			return undefined;
 		} else if (context.reason === SaveReason.EXPLICIT) {
 			saveTrigger = 'explicit';
 		} else {