Reporting results to Github

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.

Github status and check runs for Lighthouse scores and page weight

Part 1: Installing the DebugBear Github App

  1. Open the integrations tab on your project dashboard
  2. Connect your DebugBear account to Github (if you haven't done so already)
  3. Click "Install Github integration" and give access to the relevant repositories
  4. The DebugBear Github App is now installed

Message showing DebugBear Github app has been installed

Part 2: Analyzing pages in CI and reporting the results

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.

  • --repoOwner
  • --repoName
  • --commitHash

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 master or develop.

Can I analyze multiple pages in CI?

Currently you can only report monitoring results for one page to Github. Get in touch if you have multiple pages you need to monitor.


Still need help? Contact matt@debugbear.com for support.
© 2019 DebugBear Ltd