Chromatic GitHub Action

This action takes care of publishing your Storybook to Chromatic and kicking off tests if they're enabled.

It's a wrapper for chromatic-cli.

It can:

build your Storybook
publish the Storybook to Chromatic
report test results to log

it does NOT:

install dependencies

How to add a GitHub action

Create a file in your repo: .github/workflows/chromatic.yml

set it's content to:

name: "Chromatic"
on: push

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v1
    - run: |
        yarn && yarn build
    - uses: chromaui/action@v1
      with: 
        projectToken: <insert the chromatic projectToken here>
        token: ${{ secrets.GITHUB_TOKEN }}

Usage (all options)

- uses: chromaui/action@v1
  with:
    token: ${{ secrets.GITHUB_TOKEN }}
    projectToken: 'Your chromatic project token'
    buildScriptName: 'The npm script that builds your Storybook [build-storybook]'
    storybookBuildDir: 'Provide a directory with your built storybook; use if you've already built your storybook'
    allowConsoleErrors: 'do not exit when runtime errors occur in storybook'
    autoAcceptChanges: 'automatically accept all changes in chromatic: boolean or branchname'
    exitZeroOnChanges: 'positive exit of action even when there are changes: boolean or branchname'
    exitOnceUploaded: 'exit with 0 once the built version has been sent to chromatic: boolean or branchname'

We suggest you use a secret to hide the project token:

- uses: chromaui/action@v1
  with:
    token: ${{ secrets.GITHUB_TOKEN }}
    projectToken: ${{ secrets.CHROMATIC_PROJECT_TOKEN }}

You have to configure secrets in the settings tab (https://github.com/{YOUR_ORGANSATION}/{YOUR_REPOSITORY}/settings/secrets)

However if you need to be able to run this action on forked PRs you can't make it a secret, it has to be public:

- uses: chromaui/action@v1
  with:
    token: ${{ secrets.GITHUB_TOKEN }}
    projectToken: projectTokenhere

Checkout depth

In the v2 version of the actions/checkout action, there's no git history. Chromatic needs the git history in order to find the base-build.

Add fetch-depth: 0 to add full history, see: https://github.com/actions/checkout#whats-new

Development

Publish to a distribution branch

Actions are run from GitHub repos. We will create a releases branch and only commit production modules.

Comment out node_modules in .gitignore and create a releases/v1 branch

# comment out in distribution branches
# node_modules/

git checkout -b releases/v1
git commit -a -m "prod dependencies"

npm prune --production
git add node_modules
git commit -a -m "prod dependencies"
git push origin releases/v1

See the versioning documentation

Validate

You can now validate the action by referencing the releases/v1 branch

- uses: chromaui/action@releases/v1
  with:
    projectToken: ${{ secrets.CHROMATIC_PROJECT_TOKEN }}

See the actions tab for runs of this action! 🚀

Usage:

After testing you can create a v1 tag to reference the stable and tested action

- uses: chromaui/action@v1
  with:
    projectToken: ${{ secrets.CHROMATIC_PROJECT_TOKEN }}

tikolakin/action