Eric Bidelman

I see what you mean! Didn't realize there was an invitation link to collaborate on repos. I accepted your invite. Hmm, do you know of a way to work around...

An `Authorization` header with the user's oauth token would be great, but that would that work? Wouldn't that also post as the user and not the lighthouse bot profile icon?

Those might be an option. Without a proper Github Integration, I do like that users see the official name and icon: Otherwise, they're going to see themselves and their name....

@schoenwaldnils That setup looks good to me. You've got the bot as a collaborator on the repo and using an API as the Travis env https://github.com/ebidel/lighthouse-ci#get-an-api-key?

This should already be taken care of here: https://github.com/ebidel/lighthouse-ci/blob/master/frontend/server.js#L172

What do you mean when the URL is wrong?

When you run LH from the CLI on a 404 page, it gives you this and exits the process: What are you seeing?

Just did a fresh checkout and not seeing this myself when using `Dockerfile.nonheadless`. I'm using Docker 18.0.6 on Mac. > sh: 0: Can't open /chromeuser-script_nonheadless.sh Looks suspicious. Do you have...

@asayamakk try launching headful chrome with `--disable-sandbox` in https://github.com/ebidel/lighthouse-ci/blob/master/builder/chromeuser-script_nonheadless.sh or add it to `--chrome-flags` in https://github.com/ebidel/lighthouse-ci/blob/master/builder/entrypoint.sh#L6.

Docker noob here :) Do people not pre-build images and reference/use them from CI env? Or is it come to pull from the registry and build every time?