I did something similar for a self-hosted github enterprise installation: * A webhook would be fired at my host when a new pull-request was created, or updated

I did something similar for a self-hosted github enterprise installation: * A webhook would be fired at my host when a new pull-request was created, or updated. * When the webhook was received we'd store details of the repository, the branch-name, and the PR-ID into a queue, from the webhook paylad. * A bunch of worker machines would poll the queue, and when a new message was received they'd checkout the repository, run "make test", and add the output of the run as a comment to the PR. This was done as a temporary thing, rather than spinning up Jenkins/similar, with the expectation we'd get Github Actions coming to Github Enterprise in the near future.