From 875fc731995058c3bd51093dd7593272cc29eb25 Mon Sep 17 00:00:00 2001 From: G r e y Date: Thu, 26 May 2022 15:49:18 -0400 Subject: [PATCH] ci: disable chromatic on forks --- .github/workflows/chromatic.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/chromatic.yaml b/.github/workflows/chromatic.yaml index 083730a8bd4d8..0bc23ba403180 100644 --- a/.github/workflows/chromatic.yaml +++ b/.github/workflows/chromatic.yaml @@ -42,7 +42,7 @@ jobs: # storybook snapshots will require manual approval/review in order for # the check to pass. This is desired in PRs, but not in mainline. - name: Publish to Chromatic (non-mainline) - if: github.ref != 'refs/heads/main' + if: github.ref != 'refs/heads/main' && github.repository_owner == 'coder' uses: chromaui/action@v1 with: buildScriptName: "storybook:build" @@ -59,7 +59,7 @@ jobs: # commits, but it's good to be defensive in case, otherwise CI remains # infinitely "in progress" in mainline unless we re-review each build. - name: Publish to Chromatic (mainline) - if: github.ref == 'refs/heads/main' + if: github.ref == 'refs/heads/main' && github.repository_owner == 'coder' uses: chromaui/action@v1 with: autoAcceptChanges: true