🦆

Troubleshooting

Mergify Enterprise

‣

Control Panel

If you’re having issues with your Mergify installation, here’s a few items that can help you finding out the root cause.

Accessing Logs

All logs are printed to the standard output and can be read with:

$ docker logs mergify-engine

docker exec -u root -it mergify-engine /bin/bash
# mergify-admin  connectivity-check
Redis: connected
Postgres: connected
GitHub server: connected

Your must first add a healthcheck shared token in the container environment:

MERGIFYENGINE_HEALTHCHECK_SHARED_TOKEN=<a-random-token>

Then you can query the healthcheck endpoint:

curl https://mergify.example.com/healthcheck -H "Authorization: bearer <a-random-token>""
{"redis":{"status":"ok"},"postgres":{"status":"ok"}}

Here’s a checklist that can help you finding an issue with your setup

Check that webhooks are sent and receive a 202 HTTP code.

If they receive a 504 or 404 error code, make sure the event URL in the application settings is correct and ends up with /event.

You can check that GitHub events are correctly posted on the Mergify engine by looking at:

https://github.com/organizations/<my-organization>/settings/apps/<application-name>/advanced

When a pull request is created, does Mergify/Summary check-run appears?

If you don’t see it:

Table Of Contents