Billy Keyes

At the moment, there's no priority mechanism in Bulldozer: pull requests are merged in the order events are delivered and processed. You might be able to simulate this via a...

It's difficult to give advice here without knowing more about your environment and configuration, but based on the information you included, I think Bulldozer is only listening for connections on...

That error usually indicates that the server is missing configuration or the webhook configuration is incorrect. To start, can you confirm that: 1. In the Bulldozer server configuration, the `github.app.integration_id`...

The installation ID refers to the repository or organization where Bulldozer is installed. We expect that ID to be included in the event payload with webhook event send for the...

> This has been manually added to the github app configurations. It was also added to repository hook settings. You only need to add the hook to GitHub app settings....

I think you may be hitting #145. Currently, when updates are enabled by comment, the update will only happen when a change is pushed to the target branch _after_ adding...

Bulldozer will only wait for statuses that it knows about up front. This is because in general, there is no way to know when looking at a PR if all...

For any particular status, it should only need to appear in one place: either the GitHub protected branch configuration (if it applies to both humans and to Bulldozer) or the...

> If this is doable by an automated tool like Dependabot, why isn't the same thing possible for bulldozer? The unsatisfying answer is that I don't know how to do...

This makes sense to me - I believe it was only done the current way for simplicity. I'm happy to review/accept a PR implementing this. For context, we're also working...