From de23064b09cd2b762ddf6346be3fa220f16ab72c Mon Sep 17 00:00:00 2001 From: Jamie Thompson Date: Thu, 15 Apr 2021 13:14:31 +0100 Subject: [PATCH] revert: "docs: add info about chromatic for major branch" This reverts commit e6cfa9aa9433d94835fbce75ad1b962f294f4e81. --- docs/testing-styleguide.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/testing-styleguide.md b/docs/testing-styleguide.md index ce3a3c55d1..acc8a8cb2d 100644 --- a/docs/testing-styleguide.md +++ b/docs/testing-styleguide.md @@ -93,8 +93,6 @@ Where functionality is already tested in unit testing, this does not need to be [Chromatic](https://www.chromatic.com/builds?appId=5ecf782fe724630022d27d7d) is used to test for visual regressions during each build by comparing snapshots of the storybook canvas with previous baseline snapshots. Chromatic automatically snapshots every story canvas. You should not need to run Chromatic locally. -For releasing a group of `BREAKING CHANGES` we agreed to create a `major/**` branch to avoid draining `chromatic` resources. After creating the `major/**` branch we need to run `git checkout major/**` and run `npx chromatic --project-token=CHROMATIC_PROJECT_TOKEN` to manually trigger a `chromatic` build on the `major/**` branch to perform a comparison with `master`. It allows us to merge the `BREAKING CHANGES` into the `major/**` branch without running `chromatic`. - ##### Cypress File Structure ``` .