@elkuku @b2z any feedback?

Sorry for the late response, I'm currently in the jungle (literally) without any "real" internet access...

I also have to confess that I am not (yet) familiar what those "PR review comments" really are and how they are different from "code reviews comments" or "simple comments".
I guess that they are not "code related" so I wonder what could be the difference between:

• https://developer.github.com/v3/pulls/reviews/#create-a-pull-request-review and
• https://developer.github.com/v3/pulls/reviews/#submit-a-pull-request-review
  The former includes code references so maybe those are related to:
• https://developer.github.com/v3/pulls/comments/#create-a-comment ?
  so I guess this needs some testing...

Would it make sense to add a CLI script to this PR to import already existing stuff?

Test it on a live service

I wonder if it could be possible for the Joomla! project to set up such a service with access for several individuals?
I think this would ease up the development, especially with testing stuff like webhooks.

I believe the rest of your TODOs will be solved when we have a test site ?

This is a pull request review :P and you added a comment to that review. That's the comment associated with a PR review

@wilsonge how do you see the UI? We do not have code in tracker, so we will display them as simple comments?

Looks good - needs a bunch of testing

@elkuku not much wtihout UI ?

@wilsonge how do you see the UI

I'm not sure. Because you can have multiple reviews by the same person, I assume you have to do a GitHub style on the system where you display the latest review at the bottom. Maybe in the timeline it's worth saying "XXX reviewed this Pull Request" (I'm unsure whether reviews should be hidden from the UI when they are dismissed or not)

@elkuku not much wtihout UI ?

You can test this by just looking at the database entries and webhook responses as I said above I'd rather work on the UI elsewhere because I think it can become quickly rapidly.

OK So I've tested this using the CLI hook testing tool and the sample webhook data that github have in their docs at https://developer.github.com/v3/activity/events/types/#pullrequestreviewevent and at least the submission of a webhook works. Unless @mbabker can set me up to save some hook results from the live project I think the best thing to do is to publish this and start to look at what does and doesn't break.

@wilsonge Check https://github.com/joomla/joomla-cms/settings/hooks/22200574 for live payloads.