This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation.

Hi, I'm interested in this PR, actually I've even enchanced this with support of new Events (Status and PullRequestReview). But to submit my PR, I'd need this merged first.

I think only @kohsuke can do that.

Fixes #305

I have accidentally created a pull request for the same purpose (#366) and I must confess that I'm very surprised that they are similar in so many ways. Regardless of that, since this PR has been created before and has already been reviewed by a CloudBees employee, I will close mine in favour or this one.

I will do my review on this one too since we both spent a significant time working on this matter and I would love to see this merged in the short-term as some of the automation process I created at work would really benefit of it.

@kohsuke when you have a spare time, please merge it ;)

Hi, I'm interested in this PR, actually I've even enchanced this with support of new Events (Status and PullRequestReview). But to submit my PR, I'd need this merged first.

@porcelli Now that this is merged and released would you be able to issue your PR to add event support for PR reviews?

@mattnelson the new events (Status and PullRequestReview) that @porcelli mentioned were already merged in this PR: https://github.com/kohsuke/github-api/pull/363/files

@PauloMigAlmeida thanks, I missed that.

I was specifically looking for the data binding in GHEventPayload as I was wanting to implement a hook on the PullRequestReview event. If this hasn't been implemented yet, I will look into it. The rest of the parts are already there, so it should be pretty strait forward.

Hi @mattnelson

If what you want it to implement a hook based on the PullRequestReview event from GHEvent class. This is what you can do:
PS.: This is a piece of code extracted from an internal system of ours that does exactly you just described.

public class GitConfigRepositoryOperation extends AbstractGitHubOperation<Void> {

    private GHRepository repository;
    private final static String webhookUrl;

    static{
        webhookUrl = KMSEnvironmentalVariableDecryptService.getInstance().decryptKey("GitWebhookUrl");
    }

    public GitConfigRepositoryOperation(GHRepository repository) throws IOException {
        super(repository.getFullName());
        this.repository = repository;
    }

    @Override
    public Void performOperation() throws Exception {

        // Configure Webhook
        Map<String, String> configMap = new HashMap<>(2);
        configMap.put("url", webhookUrl);
        configMap.put("content_type", "json");
        this.repository.createHook("web",
                configMap,
                Arrays.asList(
                    GHEvent.PULL_REQUEST,
                    GHEvent.PULL_REQUEST_REVIEW,
                    GHEvent.PULL_REQUEST_REVIEW_COMMENT,
                    GHEvent.PUSH,
                    GHEvent.CREATE
                ), true);

        return null;
    }

Hope that it helps.