You can run DebugBear as part of your Continuous Integration process. For every commit you'll be able to see how your changes affect factors like bundle size and Lighthouse scores.
If you've set up a performance budget builds will fail if the budget is breached.
Read this how-to article for a more detailed guide to setting up CI reporting with DebugBear.
You can now use the CLI to analyze pages and report the results to Github.
Results are reported to Github if the following arguments are passed into the CLI. These can be inferred in CI environments like CircleCI or TravisCI.
You should also pass in a
--baseBranch so that your analyses are compared to other CI builds instead of the production URL. Usually the base branch will be
Currently you can only report monitoring results for one page to Github. Get in touch if you have multiple pages you need to monitor.