We don't seem to regularly address any of these PRs that are currently open, but Renovate force pushes to the PRs it currently has open. For some of the current branches, we ran what looks like >2500 builds so far.
That seems quite wasteful to me.
This makes the workflow explicit: You go to the dashboard, check the checkbox, and get the PR you want to merge in a moment.
No more crazy amount of CI jobs generated from pretty much stale PRs.
Also, most of the package specific rules felt outdated so removed them.
Once this is merged, I will close the current stale PRs (can be reopened using the dashboard) and we should ideally see less CI jobs.
* web: enable cross-theme screenshots in Chromatic
* web: use useRedesignToggle in create-chromatic-story
* web: remove redundant condition
* web: add additional comments
* web: remove unused var
* web: add comment
* web: add @storybook/client-api to dev deps
* web: handle initial redesign-theme class toggle in toolbar component
* web: remove redundant import
* Update client/branded/src/global-styles/colors-redesign.scss
Co-authored-by: Felix Becker <felix.b@outlook.com>
* web: use for of loop
* web: update renovate.md
* web: disable Chromatic workflow if no related files were changed
* web: disable renovate rebase on conflict to limit the number of Chromatic uploads
* web: update comment
* Update enterprise/dev/ci/internal/ci/is-storybook-affected.go
Co-authored-by: Tom Ross <tom@umpox.com>
* web: do not ignore .graphqlrc.yml and run Chromatic if isMasterDryRun
Co-authored-by: Felix Becker <felix.b@outlook.com>
Co-authored-by: Tom Ross <tom@umpox.com>
* Add top-level catch-all owner for new TS files
* Add dev/release to linted projects
* Standardize on the same dependencies
This reduces the amount of packages needing to be updated.
* Configure @beyang as owner for Renovate PRs
* Add TSLint
* Add yarn
