Skip to content

Commit e0a87cf

Browse files
authored
chore: fail workflow if chromatic finds changes in examples (#843)
<!-- ☝️ PR title should follow conventional commits (https://conventionalcommits.org). In particular, the title should start with one of the following types: - docs: 📖 Documentation (updates to the documentation or readme) - fix: 🐞 Bug fix (a non-breaking change that fixes an issue) - feat: ✨ New feature/enhancement (a non-breaking change that adds functionality or improves existing one) - feat!/fix!: ⚠️ Breaking change (fix or feature that would cause existing functionality to change) - chore: 🧹 Chore (updates to the build process or auxiliary tools and libraries) --> Currently the workflow passes even though there are changes in the examples. Thus, one always have to manually check the chromatic app before merging a PR, which gets tiresome. ### 🔗 Linked issue Refs #710 <!-- If it resolves an open issue, please link the issue here. For example "Resolves #123" --> ### 📚 Description <!-- Describe your changes in detail --> <!-- Why is this change required? What problem does it solve? -->
1 parent c19c93c commit e0a87cf

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

.github/workflows/ci-examples.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -61,4 +61,6 @@ jobs:
6161
# exitOnceUploaded: true
6262
projectToken: ${{ matrix.projectToken }}
6363
buildScriptName: ${{ matrix.storybookBuildScript }}
64+
# Fail workflow if changes are found
65+
exitZeroOnChanges: false
6466
debug: true

0 commit comments

Comments
 (0)