You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/workflows/dcr-chromatic.yml
+8-8Lines changed: 8 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -3,8 +3,6 @@ name: DCR Chromatic 👓
3
3
on:
4
4
merge_group:
5
5
types: [checks_requested]
6
-
push:
7
-
branches: [main]
8
6
pull_request:
9
7
types: [opened, labeled, synchronize]
10
8
@@ -21,24 +19,26 @@ jobs:
21
19
# reported. When skipping, Chromatic posts a passing status without building Storybook.
22
20
steps:
23
21
- name: Checkout - On Pull Request
24
-
uses: actions/checkout@v6
22
+
uses: actions/checkout@v7
25
23
if: ${{ github.event_name == 'pull_request'}}
26
24
with:
27
25
fetch-depth: 0
28
26
# By default the pull_request event will run on a ephermeral merge commit which simulates a merge between the pull request
29
27
# and the target branch. This can cause issues with Chromatic https://www.chromatic.com/docs/turbosnap#github-pullrequest-triggers
30
28
# Hopefully by checking out the HEAD commit of a PR instead of the merge commit we can avoid some of those issues.
31
-
ref: ${{ github.event.pull_request.head.sha }}
29
+
# We fallback to github.sha in case the workflow is triggered by a merge_group event, which doesn't have a pull_request object, see https://www.chromatic.com/docs/faq/merge-queue-ref/
0 commit comments