A list of checks we will need to run in the CI in order to save us time during development and help guarantee a high code quality:

• static analysis
  • yarn no diff / deduplicate ([test] Add yarn deduplicate step #107)
  • eslint
  • prettier no diff
  • lint JSON ([test] Lint JSON #108)
  • typescript no errors (.spec.ts) ([docs] Polish TypeScript #187)
• publishing
  • build (rollup)
  • release (codesandbox-ci) https://ci.codesandbox.io/status/mui-org/material-ui/pr/22195/builds/46193 ([test] Add codesandbox-ci #227)
• tests
  • test coverage ([test] Add codecov #3873)
  • test browsers ([test] Setup the e2e test suite (from main repo) #115)
  • puppeteer (add integration test in CI #151, [core] Setup e2e tests #1443)
• misc
  • deploy storybook ([storybook] Remove need for yarn-link #116)
  • visual screenshots ([test] Add visual regression tests #1081)
  • bundle size diff

A lot should be copied from https://github.com/mui/material-ui, the CI has been gone through numerous iterations there already. It will be much better to compound on it. Then, once we double the size of the team, I think that it could starts to make sense to diverge, exploring different directions.