From 579fd4bc893b09bfc143e529fca7571f4ce83a6c Mon Sep 17 00:00:00 2001
From: G r e y <grey@coder.com>
Date: Wed, 6 Apr 2022 18:40:30 -0400
Subject: [PATCH] chore: speed up chromatic ci (#904)

This is an oversight from #896 . It turns out that because we use the GitHub integration with Chromatic, we don't need to wait for the results to be reported in the action - they get reported in the other checks created by Chromatic.

This option was spit-out in a check:

https://github.com/coder/coder/runs/5859427236?check_suite_focus=true#step:4:38

Relates to #444
---
 .github/workflows/chromatic.yaml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/.github/workflows/chromatic.yaml b/.github/workflows/chromatic.yaml
index 17afc06892..9d38266b46 100644
--- a/.github/workflows/chromatic.yaml
+++ b/.github/workflows/chromatic.yaml
@@ -32,6 +32,7 @@ jobs:
         uses: chromaui/action@v1
         with:
           buildScriptName: "storybook:build"
+          exitOnceUploaded: true
           projectToken: ${{ secrets.CHROMATIC_PROJECT_TOKEN }}
           workingDir: "./site"