From 08c2a72907838f8466bfff91f1deff2dc1bccd57 Mon Sep 17 00:00:00 2001
From: Simon H <5968653+dummdidumm@users.noreply.github.com>
Date: Wed, 26 Aug 2026 11:29:50 +0200
Subject: [PATCH] chore: set Vitest reporter for github actions (#18722)

test failures show up really bad now, minimal is way better for github actions
---
 vitest.config.js | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/vitest.config.js b/vitest.config.js
index 116dfae9d8..faabcfbea4 100644
--- a/vitest.config.js
+++ b/vitest.config.js
@@ -28,7 +28,7 @@ export default defineConfig({
 	},
 	test: {
 		dir: '.',
-		reporters: ['dot'],
+		reporters: process.env.GITHUB_ACTIONS === 'true' ? ['minimal'] : ['dot'],
 		// A handful of dev-mode tests trigger Svelte's `effect_update_depth_exceeded`
 		// guard, which involves ~1000 Error objects per flush for stack tracking —
 		// slow enough under vitest 4's deeper async stacks (and CI's slower workers)