Skip to content

Commit

Permalink
chore: fail workflow if chromatic finds changes in examples (#843)
Browse files Browse the repository at this point in the history
<!--
☝️ 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? -->
  • Loading branch information
tobiasdiez authored Jan 16, 2025
1 parent c19c93c commit e0a87cf
Showing 1 changed file with 2 additions and 0 deletions.
2 changes: 2 additions & 0 deletions .github/workflows/ci-examples.yml
Original file line number Diff line number Diff line change
Expand Up @@ -61,4 +61,6 @@ jobs:
# exitOnceUploaded: true
projectToken: ${{ matrix.projectToken }}
buildScriptName: ${{ matrix.storybookBuildScript }}
# Fail workflow if changes are found
exitZeroOnChanges: false
debug: true

0 comments on commit e0a87cf

Please sign in to comment.