diff --git a/.github/workflows/ar-chromatic.yml b/.github/workflows/ar-chromatic.yml deleted file mode 100644 index 08467f90dd8..00000000000 --- a/.github/workflows/ar-chromatic.yml +++ /dev/null @@ -1,51 +0,0 @@ -name: AR Chromatic 👓 - -on: - push: - branches: [main] - pull_request: - types: [opened, labeled, synchronize] - -jobs: - chromatic: - name: Chromatic - runs-on: ubuntu-latest - # Run Chromatic only if `run_chromatic` label has been applied or we're - # pushing to `main`. Skip if this is a Dependabot PR as this is handled - # by the subsequent job. - if: | - (contains(github.event.pull_request.labels.*.name, 'run_chromatic') || github.ref == 'refs/heads/main') && - (!contains(github.event.pull_request.labels.*.name, 'dependencies') && - github.event.pull_request.user.login != 'dependabot') - steps: - - name: Checkout - On Pull Request - uses: actions/checkout@v5 - if: ${{ github.event_name == 'pull_request'}} - with: - fetch-depth: 0 - # By default the pull_request event will run on a ephermeral merge commit which simulates a merge between the pull request - # and the target branch. This can cause issues with Chromatic https://www.chromatic.com/docs/turbosnap#github-pullrequest-triggers - # Hopefully by checking out the HEAD commit of a PR instead of the merge commit we can avoid some of those issues. - ref: ${{ github.event.pull_request.head.sha }} - - name: Checkout - On Push Event - uses: actions/checkout@v5 - if: ${{ github.event_name == 'push'}} - with: - fetch-depth: 0 - - - name: Set up Node environment - uses: ./.github/actions/setup-node-env - - - name: Chromatic - Apps Rendering - env: - NODE_OPTIONS: '--max_old_space_size=4096' - uses: chromaui/action@v13.3.0 - - with: - projectToken: ${{ secrets.CHROMATIC_PROJECT_TOKEN__APPS_RENDERING }} - token: ${{ secrets.GITHUB_TOKEN }} - untraced: '**/(package*.json|pnpm-lock.yaml|preview.js)' - exitOnceUploaded: true - onlyChanged: '!(main)' # only turbosnap on non-main branches - workingDir: apps-rendering - buildScriptName: 'build-storybook'